CVE-2026-44190

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw was found in the Ansible Lightspeed Visual Studio Code extension. This Command Injection vulnerability (CWE-78) allows a remote attacker to execute unauthorized commands on a user's system. The issue occurs because the ansible.python.activationScript setting, intended for a virtual environment activation script, does not properly validate user input as a file path. If a user opens or executes a specially crafted project, an attacker could exploit this to gain complete control over the user's system with the privileges of the Visual Studio Code application.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
—
KEV
Not listed

Published

July 22, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
Patch available. Sources: redhat.
redhat

2466762 – (CVE-2026-44190) CVE-2026-44190 ansible-lightspeed: Ansible Lightspeed Visual Studio Code extension: Arbitrary code execution via command injection in activation script setting

https://bugzilla.redhat.com/show_bug.cgi?id=2466762
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-44190

Vendor Advisories for CVE-2026-44190(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 75× in last 7d / 75× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 20:54 UTCGHSA enrichment
  2. 2026-07-22 20:31 UTCGHSA enrichment
  3. 2026-07-22 20:30 UTCGHSA enrichment
  4. 2026-07-22 20:01 UTCGHSA enrichment
  5. 2026-07-22 19:58 UTCGHSA enrichment
  6. 2026-07-22 19:58 UTCGHSA enrichment
  7. 2026-07-22 19:55 UTCGHSA enrichment
  8. 2026-07-22 19:54 UTCGHSA enrichment
  9. 2026-07-22 19:51 UTCGHSA enrichment
  10. 2026-07-22 19:51 UTCGHSA enrichment
  11. 2026-07-22 19:50 UTCGHSA enrichment
  12. 2026-07-22 19:48 UTCGHSA enrichment
  13. 2026-07-22 19:47 UTCGHSA enrichment
  14. 2026-07-22 19:46 UTCGHSA enrichment
  15. 2026-07-22 19:44 UTCGHSA enrichment
  16. 2026-07-22 19:43 UTCGHSA enrichment
  17. 2026-07-22 19:41 UTCGHSA enrichment
  18. 2026-07-22 19:40 UTCGHSA enrichment
  19. 2026-07-22 19:39 UTCGHSA enrichment
  20. 2026-07-22 19:38 UTCGHSA enrichment
  21. 2026-07-22 19:38 UTCGHSA enrichment
  22. 2026-07-22 19:37 UTCGHSA enrichment
  23. 2026-07-22 19:36 UTCGHSA enrichment
  24. 2026-07-22 19:34 UTCGHSA enrichment
  25. 2026-07-22 19:33 UTCGHSA enrichment
Show 50 more
  1. 2026-07-22 19:31 UTCGHSA enrichment
  2. 2026-07-22 19:30 UTCGHSA enrichment
  3. 2026-07-22 19:29 UTCGHSA enrichment
  4. 2026-07-22 19:28 UTCGHSA enrichment
  5. 2026-07-22 19:27 UTCGHSA enrichment
  6. 2026-07-22 19:26 UTCGHSA enrichment
  7. 2026-07-22 19:26 UTCGHSA enrichment
  8. 2026-07-22 19:25 UTCGHSA enrichment
  9. 2026-07-22 19:24 UTCGHSA enrichment
  10. 2026-07-22 19:23 UTCGHSA enrichment
  11. 2026-07-22 19:21 UTCGHSA enrichment
  12. 2026-07-22 19:19 UTCGHSA enrichment
  13. 2026-07-22 19:15 UTCGHSA enrichment
  14. 2026-07-22 19:13 UTCGHSA enrichment
  15. 2026-07-22 19:00 UTCGHSA enrichment
  16. 2026-07-22 18:59 UTCGHSA enrichment
  17. 2026-07-22 18:51 UTCGHSA enrichment
  18. 2026-07-22 18:49 UTCGHSA enrichment
  19. 2026-07-22 18:47 UTCGHSA enrichment
  20. 2026-07-22 18:46 UTCGHSA enrichment
  21. 2026-07-22 18:45 UTCGHSA enrichment
  22. 2026-07-22 18:45 UTCGHSA enrichment
  23. 2026-07-22 18:43 UTCGHSA enrichment
  24. 2026-07-22 18:34 UTCGHSA enrichment
  25. 2026-07-22 18:31 UTCGHSA enrichment
  26. 2026-07-22 18:29 UTCGHSA enrichment
  27. 2026-07-22 18:27 UTCGHSA enrichment
  28. 2026-07-22 18:22 UTCGHSA enrichment
  29. 2026-07-22 18:20 UTCGHSA enrichment
  30. 2026-07-22 18:18 UTCGHSA enrichment
  31. 2026-07-22 18:17 UTCGHSA enrichment
  32. 2026-07-22 18:14 UTCGHSA enrichment
  33. 2026-07-22 18:13 UTCGHSA enrichment
  34. 2026-07-22 17:53 UTCGHSA enrichment
  35. 2026-07-22 17:51 UTCGHSA enrichment
  36. 2026-07-22 17:49 UTCGHSA enrichment
  37. 2026-07-22 17:48 UTCGHSA enrichment
  38. 2026-07-22 17:47 UTCGHSA enrichment
  39. 2026-07-22 17:41 UTCGHSA enrichment
  40. 2026-07-22 17:35 UTCGHSA enrichment
  41. 2026-07-22 17:28 UTCGHSA enrichment
  42. 2026-07-22 17:26 UTCGHSA enrichment
  43. 2026-07-22 17:25 UTCGHSA enrichment
  44. 2026-07-22 17:22 UTCGHSA enrichment
  45. 2026-07-22 17:19 UTCGHSA enrichment
  46. 2026-07-22 17:17 UTCGHSA enrichment
  47. 2026-07-22 13:35 UTCEG score recompute
  48. 2026-07-22 13:35 UTCGHSA enrichment
  49. 2026-07-22 12:13 UTCEG score recompute
  50. 2026-07-22 12:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-44190?
CVE-2026-44190 is a high vulnerability published on July 22, 2026. A flaw was found in the Ansible Lightspeed Visual Studio Code extension. This Command Injection vulnerability (CWE-78) allows a remote attacker to execute unauthorized commands on a user's system. The issue occurs because the ansible.python.activationScript setting, intended for a virtual…
When was CVE-2026-44190 disclosed?
CVE-2026-44190 was first published in the National Vulnerability Database on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-44190?
CVE-2026-44190 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-44190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44190, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-44190

Explore →

Is Your Infrastructure Affected by CVE-2026-44190?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs