AI Stack Alert High CVE-2026-129877 For CISO, SOC / IR, AppSec, AI Eng AI-assisted
DeepAudit 2.0.0-beta.1 through 3.8.0 leaks LLM API keys and GitHub/GitLab tokens via /api/v1/config/defaults
DeepAudit versions 2.0.0-beta.1 through 3.8.0 contain an information disclosure vulnerability. An unauthenticated attacker can send a GET request to /api/v1/config/defaults to retrieve server secrets. The exposed secrets include the operator's LLM provider API keys and GitHub or GitLab tokens.
Why it matters
Any network-reachable DeepAudit instance exposes its LLM and source-control credentials to unauthenticated users. An attacker could use those keys to run up provider costs and access repositories the tokens can reach.
Do this
- Upgrade DeepAudit to a version later than 3.8.0 once a fixed release is confirmed in the vendor advisory.
- Restrict network access to DeepAudit instances so the /api/v1/config/defaults endpoint is not reachable from untrusted networks.
- Rotate LLM provider API keys and GitHub or GitLab tokens used by any DeepAudit deployment in the affected range.
- Review provider and source-control audit logs for unexpected API usage or repository access originating from DeepAudit credentials.
- Search web server and reverse proxy logs for unauthenticated GET requests to /api/v1/config/defaults.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 8.7CVSS
- NoPublic PoC
- 36/100Priority
- 80%Confidence
Evidence
“contains an information disclosure vulnerability that allows unauthenticated attackers to retrieve server secrets through the /api/v1/config/defaults endpoint”
“Attackers can send a GET request to obtain the operator's LLM provider API keys and GitHub or GitLab tokens”
Sources
Affected / related
DeepAudit, GitHub, GitLab, Information disclosure
Published 2026-11-16 15:17 UTC · updated 2026-11-16 16:35 UTC · AI-assisted summary, checked against quoted sources · How we score