CVE-2026-129877
DeepAudit exposed model-provider keys and repository tokens
DeepAudit project · DeepAudit code-auditing platform
First documented disclosure · Review checkpoint
Summary
DeepAudit could return server-wide model-provider credentials and repository tokens to an unauthenticated client.
Severity and exploitation evidence
High · 8.7/10 · CVSS 4.0. Severity source.
Exploitation not established: The sources reviewed identify no confirmed malicious use.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
A configuration response included stored secrets.
Conditions required
Network access to an affected deployment that stores provider keys or repository tokens.
Potential impact
A caller could consume paid model services or use the repositories accessible to the exposed tokens.
Affected versions and configurations
2.0.0-beta.1 through 3.8.0.
Fix and mitigation status
No corrected release identified.
Practical next steps
Restrict access to configuration responses and rotate credentials that an exposed deployment stored. Review provider usage and repository access.
Operating lesson
Return secret presence or metadata in configuration views and keep credential values server-side.
Evidence and limits
The original researcher report dates this finding to November 6. VulnCheck published the CVE on November 16. The reviewed sources identify no corrected release.
Sources
- Wu Yulun’s dated report index, DeepAudit
Primary source ·
- VulnCheck CVE record
Primary source ·
- VulnCheck security advisory
Primary source ·