Quick Take
- What: DeepAudit 2.0.0-beta.1 through 3.8.0 exposes LLM API keys and Git tokens via an unauthenticated endpoint.
- Who is affected: Any organization running DeepAudit versions 2.0.0-beta.1 through 3.8.0 with configured LLM provider keys or GitHub/GitLab tokens.
- CVE: CVE-2026-129877, CVSS 7.5 (high severity).
- What to do: Rotate all LLM provider API keys and GitHub/GitLab tokens immediately, then upgrade to a patched version when available.
In plain English
DeepAudit is a developer tool that uses AI to audit code. A security flaw in versions 2.0.0-beta.1 through 3.8.0 lets anyone on the internet read the server’s secret keys without logging in. These secrets include API keys for AI services like OpenAI, Claude, and Gemini, plus tokens for GitHub and GitLab. An attacker can use these keys to run up bills on your AI accounts or access your private code repositories.
What you should do: If you run DeepAudit, you need to change all those keys and tokens right away. If you don’t use DeepAudit, you can ignore this.
What happened
DeepAudit versions 2.0.0-beta.1 through 3.8.0 contain an information disclosure vulnerability tracked as CVE-2026-129877. The vulnerability exists in the /api/v1/config/defaults endpoint, which returns server configuration data without requiring authentication.
According to the vulnerability report, an attacker can send a GET request to this endpoint and retrieve the operator’s LLM provider API keys and GitHub or GitLab tokens. The vulnerable code is present in the backend/app/api/v1/endpoints/config.py file at lines 109 through 154 in commit 9aa46568f20b2ab2dbc1878a4479392012c1230a.
The exposed secrets include API keys for multiple LLM providers (OpenAI, Claude, Gemini, Qwen, DeepSeek, Zhipu, Moonshot, Baidu, Minimax, and Doubao) as well as GitHub and GitLab access tokens. Once obtained, these credentials can be used to abuse the associated services and access repositories that the tokens have permission to reach.
The vulnerability was discovered by Wu Yulun and disclosed on November 6, 2026. The National Vulnerability Database assigned it a CVSS score of 7.5 (high severity), while VulnCheck assigned a CVSS v4 score of 8.7.
What you should do
If you operate a DeepAudit instance running versions 2.0.0-beta.1 through 3.8.0, you should immediately rotate all LLM provider API keys and GitHub or GitLab tokens that were configured in the system. Assume these credentials have been compromised.
The sources do not state whether a patched version is available. Monitor the DeepAudit GitHub repository for security updates and apply them as soon as they are released.
Review access logs for the /api/v1/config/defaults endpoint to determine whether unauthorized parties accessed the configuration data.
What it means
This vulnerability represents a critical failure in authentication controls for sensitive configuration data. The exposure of LLM provider API keys can lead to unauthorized usage charges and potential data exfiltration if the keys have access to fine-tuned models or stored prompts. The exposure of GitHub or GitLab tokens can grant attackers access to private source code repositories, potentially leading to intellectual property theft or supply chain attacks.
The vulnerability affects all DeepAudit installations from version 2.0.0-beta.1 through 3.8.0, a range that includes both beta and stable releases. Organizations using DeepAudit for code auditing should treat this as a high-priority security incident requiring immediate credential rotation and system review.
Leaked AI provider keys are a recurring pattern. The Railway breach led to $740,000 in unauthorized charges, and the Hugo Blog AI Proxy exposed API keys without authentication. New cases are tracked in our AI Security hub.
Sources
- NVD CVE-2026-129877
- DeepAudit vulnerable code on GitHub
- DeepAudit Vulnerability Report
- VulnCheck Advisory



