# CVE-2026-44187: Information disclosure in Red Hat Ansible Automation Platform 2

> Local attackers can read the Google Gemini API key stored in plain text by the Ansible Lightspeed VS Code extension, leading to credential theft.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-fxgw-9xvp-9r43

## What is CVE-2026-44187?

CVE-2026-44187 is a low-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2026-44187?


## How do I fix CVE-2026-44187?

No fix has been published for CVE-2026-44187 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44187 being exploited?

There is no known exploitation of CVE-2026-44187 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44187 and fix it if it is affected.

What it is: CVE-2026-44187 is a low-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44187 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44187/ (Markdown: https://insights.sbomify.com/CVE-2026-44187/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44187
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44187
- OSV: https://osv.dev/vulnerability/CVE-2026-44187

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44187/
Summaries are generated and may contain mistakes; the official description above is the record.