Skip to content
Fencer Vulns
low 3.3

CVE-2026-44187 json

Ansible-lightspeed: ansible lightspeed extension for visual studio code: information disclosure of google gemini api key

published 2026-07-22 3 mo ago modified 2026-10-24 16 d ago also EUVD-2026-47653

cvss
3.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-44187 updated cvss 3.3

ansible-lightspeed: Ansible Lightspeed extension for Visual Studio Code: Information disclosure of Google Gemini API key

  • Red Hat Ansible Automation Platform 2 ansible-dev-tools, ansible-automation-platform-25/ansible-dev-tools-rhel8, ansible-automation-platform-26/ansible-dev-tools-rhel9
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Red Hat Red Hat Ansible Automation Platform 2

Classification

Weakness
  • CWE-256 Plaintext Storage of a Password

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.