CVE-2026-129880
DeepAudit could send repository credentials to an untrusted host
DeepAudit project · DeepAudit code-auditing platform
First documented disclosure · Review checkpoint
Summary
A registered user could cause DeepAudit to send a shared GitLab or Gitea token to an untrusted repository host.
Severity and exploitation evidence
High · 8.3/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
The project branch-listing service attached a server-wide credential to a destination chosen for the project.
Conditions required
A registered user able to configure a repository project on a deployment with a shared repository credential.
Potential impact
Repository tokens could be disclosed and the service could contact internal hosts.
Affected versions and configurations
2.0.0-beta.5 through 3.8.0.
Fix and mitigation status
No corrected release identified.
Practical next steps
Allow only approved repository origins, restrict outbound network access and rotate shared tokens that may have been exposed.
Operating lesson
Bind each credential to its intended host before attaching it to a request.
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 ·