CVE-2026-44187

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: None knownExposed: 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 extension for Visual Studio Code. This vulnerability allows an attacker with local access to the workstation, or malware running with the user's privileges, to read the Google Gemini API key. The extension insecurely stores the API key in plain text within the user's configuration file and writes it to output log files. This information disclosure can lead to the attacker obtaining the API credential and potentially consuming the user's API quota.

CVSS v3
3.3
EG Score
3.3(medium)
EG Risk
15(Track)
EG Risk 15/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 computed
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 22, 2026

References (2)

Vendor Advisories for CVE-2026-44187(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 9× in last 7d / 39× 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-09-14 05:35 UTCEG score recompute
  2. 2026-09-14 05:35 UTCGHSA enrichment
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-12 15:01 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 09:37 UTCEPSS rescore
  7. 2026-09-11 03:18 UTCEG score recompute
  8. 2026-09-11 03:18 UTCGHSA enrichment
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 21:42 UTCEG score recompute
  12. 2026-09-07 21:42 UTCGHSA enrichment
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 13:56 UTCEG score recompute
  16. 2026-09-04 13:56 UTCGHSA enrichment
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:12 UTCEPSS rescore
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-30 00:56 UTCEG score recompute
  23. 2026-08-30 00:56 UTCGHSA enrichment
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 54 more
  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-26 08:30 UTCEG score recompute
  3. 2026-08-26 08:30 UTCGHSA enrichment
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-23 06:14 UTCEG score recompute
  6. 2026-08-23 06:14 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-20 03:58 UTCEG score recompute
  9. 2026-08-20 03:58 UTCGHSA enrichment
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 01:42 UTCEG score recompute
  14. 2026-08-17 01:42 UTCGHSA enrichment
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-13 23:26 UTCEG score recompute
  17. 2026-08-13 23:26 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-10 21:10 UTCEG score recompute
  20. 2026-08-10 21:10 UTCGHSA enrichment
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 18:54 UTCEG score recompute
  24. 2026-08-07 18:54 UTCGHSA enrichment
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-04 16:38 UTCEG score recompute
  27. 2026-08-04 16:38 UTCGHSA enrichment
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-03 10:36 UTCEPSS rescore
  30. 2026-08-02 02:27 UTCEPSS rescore
  31. 2026-08-01 14:22 UTCEG score recompute
  32. 2026-08-01 14:22 UTCGHSA enrichment
  33. 2026-08-01 04:16 UTCEPSS rescore
  34. 2026-07-30 16:28 UTCEPSS rescore
  35. 2026-07-29 12:06 UTCEG score recompute
  36. 2026-07-29 12:06 UTCGHSA enrichment
  37. 2026-07-28 15:36 UTCEPSS rescore
  38. 2026-07-27 14:13 UTCEPSS rescore
  39. 2026-07-26 14:54 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-26 09:50 UTCEG score recompute
  42. 2026-07-26 09:49 UTCGHSA enrichment
  43. 2026-07-25 14:18 UTCEPSS rescore
  44. 2026-07-24 14:17 UTCEPSS rescore
  45. 2026-07-23 14:18 UTCEPSS rescore
  46. 2026-07-23 03:14 UTCEG score recompute
  47. 2026-07-22 18:59 UTCEG score recompute
  48. 2026-07-22 18:59 UTCGHSA enrichment
  49. 2026-07-22 16:33 UTCEG score recompute
  50. 2026-07-22 16:33 UTCGHSA enrichment
  51. 2026-07-22 13:35 UTCEG score recompute
  52. 2026-07-22 13:35 UTCGHSA enrichment
  53. 2026-07-22 12:13 UTCEG score recompute
  54. 2026-07-22 12:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-44187?
CVE-2026-44187 is a low vulnerability published on July 22, 2026. A flaw was found in the Ansible Lightspeed extension for Visual Studio Code. This vulnerability allows an attacker with local access to the workstation, or malware running with the user's privileges, to read the Google Gemini API key. The extension insecurely stores the API key in plain text within…
When was CVE-2026-44187 disclosed?
CVE-2026-44187 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.
Is CVE-2026-44187 actively exploited?
CVE-2026-44187 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-44187?
CVE-2026-44187 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-44187?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44187, 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-44187

Explore →

Is Your Infrastructure Affected by CVE-2026-44187?

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

Start Free Scan →Browse All CVEs