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.
CVE-2026-44190
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.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 36%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 22, 20262466762 – (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=2466762Vendor 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 27× in last 7d / 108× 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.
Showing the most recent 100 of 108 total refreshes for this CVE.
- 2026-08-01 06:38 UTCEG score recompute
- 2026-08-01 06:38 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 18:18 UTCGHSA enrichment
- 2026-07-31 06:04 UTCGHSA enrichment
- 2026-07-30 17:48 UTCEG score recompute
- 2026-07-30 17:48 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 05:34 UTCEG score recompute
- 2026-07-30 05:34 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 17:18 UTCGHSA enrichment
- 2026-07-29 05:04 UTCGHSA enrichment
- 2026-07-28 16:50 UTCEG score recompute
- 2026-07-28 16:50 UTCGHSA enrichment
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-28 04:26 UTCGHSA enrichment
- 2026-07-27 16:12 UTCEG score recompute
- 2026-07-27 16:11 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 03:57 UTCGHSA enrichment
- 2026-07-26 15:43 UTCEG score recompute
- 2026-07-26 15:43 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-26 03:29 UTCEG score recompute
- 2026-07-26 03:29 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:14 UTCEG score recompute
- 2026-07-22 22:06 UTCEG score recompute
- 2026-07-22 22:05 UTCGHSA enrichment
- 2026-07-22 20:54 UTCGHSA enrichment
- 2026-07-22 20:31 UTCGHSA enrichment
- 2026-07-22 20:30 UTCGHSA enrichment
- 2026-07-22 20:01 UTCGHSA enrichment
- 2026-07-22 19:58 UTCGHSA enrichment
- 2026-07-22 19:58 UTCGHSA enrichment
- 2026-07-22 19:55 UTCGHSA enrichment
- 2026-07-22 19:54 UTCGHSA enrichment
- 2026-07-22 19:51 UTCGHSA enrichment
- 2026-07-22 19:51 UTCGHSA enrichment
- 2026-07-22 19:50 UTCGHSA enrichment
- 2026-07-22 19:48 UTCGHSA enrichment
- 2026-07-22 19:47 UTCGHSA enrichment
- 2026-07-22 19:46 UTCGHSA enrichment
- 2026-07-22 19:44 UTCGHSA enrichment
- 2026-07-22 19:43 UTCGHSA enrichment
- 2026-07-22 19:41 UTCGHSA enrichment
- 2026-07-22 19:40 UTCGHSA enrichment
- 2026-07-22 19:39 UTCGHSA enrichment
- 2026-07-22 19:38 UTCGHSA enrichment
- 2026-07-22 19:38 UTCGHSA enrichment
- 2026-07-22 19:37 UTCGHSA enrichment
- 2026-07-22 19:36 UTCGHSA enrichment
- 2026-07-22 19:34 UTCGHSA enrichment
- 2026-07-22 19:33 UTCGHSA enrichment
- 2026-07-22 19:31 UTCGHSA enrichment
- 2026-07-22 19:30 UTCGHSA enrichment
- 2026-07-22 19:29 UTCGHSA enrichment
- 2026-07-22 19:28 UTCGHSA enrichment
- 2026-07-22 19:27 UTCGHSA enrichment
- 2026-07-22 19:26 UTCGHSA enrichment
- 2026-07-22 19:26 UTCGHSA enrichment
- 2026-07-22 19:25 UTCGHSA enrichment
- 2026-07-22 19:24 UTCGHSA enrichment
- 2026-07-22 19:23 UTCGHSA enrichment
- 2026-07-22 19:21 UTCGHSA enrichment
- 2026-07-22 19:19 UTCGHSA enrichment
- 2026-07-22 19:15 UTCGHSA enrichment
- 2026-07-22 19:13 UTCGHSA enrichment
- 2026-07-22 19:00 UTCGHSA enrichment
- 2026-07-22 18:59 UTCGHSA enrichment
- 2026-07-22 18:51 UTCGHSA enrichment
- 2026-07-22 18:49 UTCGHSA enrichment
- 2026-07-22 18:47 UTCGHSA enrichment
- 2026-07-22 18:46 UTCGHSA enrichment
- 2026-07-22 18:45 UTCGHSA enrichment
- 2026-07-22 18:45 UTCGHSA enrichment
- 2026-07-22 18:43 UTCGHSA enrichment
- 2026-07-22 18:34 UTCGHSA enrichment
- 2026-07-22 18:31 UTCGHSA enrichment
- 2026-07-22 18:29 UTCGHSA enrichment
- 2026-07-22 18:27 UTCGHSA enrichment
- 2026-07-22 18:22 UTCGHSA enrichment
- 2026-07-22 18:20 UTCGHSA enrichment
- 2026-07-22 18:18 UTCGHSA enrichment
- 2026-07-22 18:17 UTCGHSA enrichment
- 2026-07-22 18:14 UTCGHSA enrichment
- 2026-07-22 18:13 UTCGHSA enrichment
- 2026-07-22 17:53 UTCGHSA enrichment
- 2026-07-22 17:51 UTCGHSA enrichment
- 2026-07-22 17:49 UTCGHSA enrichment
- 2026-07-22 17:48 UTCGHSA enrichment
- 2026-07-22 17:47 UTCGHSA enrichment
- 2026-07-22 17:41 UTCGHSA enrichment
- 2026-07-22 17:35 UTCGHSA enrichment
- 2026-07-22 17:28 UTCGHSA enrichment
- 2026-07-22 17:26 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-44190?
When was CVE-2026-44190 disclosed?
Is CVE-2026-44190 actively exploited?
What is the CVSS score of CVE-2026-44190?
How do I remediate CVE-2026-44190?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-44190
Is Your Infrastructure Affected by CVE-2026-44190?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.