CVE
DeepAudit token leak via SSRF in branch listing
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions 2.0.0-beta.5 through 3.8.0 Project uses a GitLab or Gitea repository source pointing to a host the attacker controls
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
DeepAudit 2.0.0-beta.5 through 3.8.0 contains a server-side request forgery vulnerability that allows registered users to leak server-wide GitLab or Gitea tokens via repository_url. Attackers can create a gitlab or gitea project pointing to a controlled host and request its branches to capture the operator's token and reach internal hosts.
Who should check
Teams running lintsinghua DeepAudit 2.0.0-beta.5 through 3.8.0 that let users add GitLab or Gitea repositories
“DeepAudit 2.0.0-beta.5 through 3.8.0 contains a server-side request forgery vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 28 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions 2.0.0-beta.5 through 3.8.0 Project uses a GitLab or Gitea repository source pointing to a host the attacker controlsWorkaround: The checked facts name no workaround. Until a fix is published, the vendor's advisory is the place to look for guidance on limiting the GitLab and Gitea repository source feature.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129880 (DeepAudit 2.0.0-beta.5 through 3.8.0 SSRF via Project Branch Listing Leaks Git Tokens), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129880 (entry last updated 2026-11-16):
Affected:
- lintsinghua DeepAudit: from 2.0.0-beta.5, through 3.8.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected versions 2.0.0-beta.5 through 3.8.0 (source: https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.5-through-3.8.0-ssrf-via-project-branch-listing-leaks-git-tokens)
- Project uses a GitLab or Gitea repository source pointing to a host the attacker controls (source: https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.5-through-3.8.0-ssrf-via-project-branch-listing-leaks-git-tokens)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129880 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129880 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vul.yulun.ac.cn/20261106/deepaudit/
- https://github.com/lintsinghua/DeepAudit/blob/9aa46568f20b2ab2dbc1878a4479392012c1230a/backend/app/utils/repo_utils.py#L38-L68
- https://github.com/lintsinghua/DeepAudit/blob/9aa46568f20b2ab2dbc1878a4479392012c1230a/backend/app/services/scanner.py#L122-L152
- https://github.com/lintsinghua/DeepAudit/blob/9aa46568f20b2ab2dbc1878a4479392012c1230a/backend/app/api/v1/endpoints/projects.py#L720-L760
- https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.5-through-3.8.0-ssrf-via-project-branch-listing-leaks-git-tokens
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129880
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129880"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- lintsinghua DeepAudit
From 2.0.0-beta.5 · through 3.8.0
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Repository
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129880
Is CVE-2026-129880 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A registered user can create a GitLab or Gitea project that points to a host the attacker controls, which makes the server reach that host. This leaks the server-wide GitLab or Gitea token to the attacker and lets the attacker reach internal hosts.Source: vulncheck.com
Which versions are affected by CVE-2026-129880?
DeepAudit: from 2.0.0-beta.5 through 3.8.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 2.0.0-beta.5 through 3.8.0 are in the affected range. The setup involves a project that uses a GitLab or Gitea repository source pointing to a host the attacker controls. A reader can compare their installed DeepAudit version with that range and check whether any project uses a GitLab or Gitea repository source.Source: vulncheck.com
How do I fix CVE-2026-129880?
The checked facts name no fixed version and no vendor patch, so no upgrade target can be given from them. Check the vendor's advisory for a fixed version or patch identifiers.Source: vulncheck.com
What if there's no patch?
The checked facts name no workaround. Until a fix is published, the vendor's advisory is the place to look for guidance on limiting the GitLab and Gitea repository source feature.Source: vulncheck.com