No analysis available yet.
Vendor Workaround
Users should immediately rotate and remove any exposed Google Gemini API keys. The API key entry must be manually removed from the ~/.config/Code/User/settings.json file. Additionally, ensure secure handling or purging of log files that may contain the API key.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 22 Jul 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Ansible-lightspeed: ansible lightspeed extension for visual studio code: information disclosure of google gemini api key | |
| First Time appeared |
Redhat
Redhat ansible Automation Platform |
|
| Weaknesses | CWE-256 | |
| CPEs | cpe:/a:redhat:ansible_automation_platform:2 | |
| Vendors & Products |
Redhat
Redhat ansible Automation Platform |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-07-22T12:06:50.258Z
Reserved: 2026-05-05T15:02:54.443Z
Link: CVE-2026-44187
No data.
No data.
No data.
OpenCVE Enrichment
No data.
-
CWE-256
Plaintext Storage of a Password