CVE-2026-44187
Awaiting Analysis Awaiting Analysis - Queue

Information Disclosure in Ansible Lightspeed VS Code Extension

Vulnerability report for CVE-2026-44187, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-22

Last updated on: 2026-07-22

Assigner: Red Hat, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-22
Last Modified
2026-07-22
Generated
2026-08-11
AI Q&A
2026-07-22
EPSS Evaluated
2026-08-10
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
redhat ansible_lightspeed *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-256 The product stores a password in plaintext within resources such as memory or files.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is in the Ansible Lightspeed extension for Visual Studio Code. It allows an attacker with local access or malware running as the user to read the Google Gemini API key stored in plain text in the user's configuration file or log files. This could lead to unauthorized use of the user's API quota.

Detection Guidance

Check the Ansible Lightspeed extension configuration files and log files for plain text storage of the Google Gemini API key. Search for files containing 'gemini' or 'api' in their content within the extension's directory or user configuration folders.

Impact Analysis

If exploited, this vulnerability could allow an attacker to access your Google Gemini API key. They could then use your API quota, potentially leading to unexpected costs or service disruptions for your account.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by exposing sensitive API keys that may be used for processing personal or health data. Unauthorized access to API keys could lead to data breaches, violating confidentiality requirements under these regulations.

Mitigation Strategies

Remove the stored API key from configuration files and log files. Update the Ansible Lightspeed extension to the latest version if a patch is available. Revoke and regenerate the compromised Google Gemini API key to prevent unauthorized usage.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44187. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart