---
id: "CVE-2026-129880"
page: "https://infrastack.ai/live/CVE-2026-129880"
kind: "vulnerability"
aliases: ["CVE-2026-129880"]
title: "DeepAudit: registered users can steal server-wide GitLab or Gitea tokens"
severity: "high"
cvss: 8.3
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "DeepAudit", "fixed": [], "affected": ">= 2.0.0-beta.5, <= 3.8.0", "ecosystem": "github"}]
ecosystems: []
tags: ["ai-tooling", "deepaudit", "gitea", "gitlab", "self-hosted", "ssrf"]
not_affected_if: ["auth-required", "no-server-wide-gitlab-gitea-token", "no-shared-git-token", "registration-closed"]
published_at: "2026-11-16T15:17:27+00:00"
first_seen_at: "2026-11-16T15:37:54+00:00"
updated_at: "2026-11-16T15:41:37+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-129880", "first_seen_at": "2026-11-16T15:37:54+00:00"}, {"source": "analyst", "url": "https://vul.yulun.ac.cn/20261106/deepaudit/", "first_seen_at": "2026-11-16T15:41:37+00:00", "cites": ["https://vul.yulun.ac.cn/20261106/deepaudit/"]}]
exploit_sources: []
---

# DeepAudit: registered users can steal server-wide GitLab or Gitea tokens

Link for people: https://infrastack.ai/live/CVE-2026-129880 (this .md is for agents)

VulnCheck says DeepAudit 2.0.0-beta.5 through 3.8.0 has an SSRF: a registered user can create a gitlab or gitea project whose repository_url points to a host they control, then request its branches; the server sends the operator's GitLab or Gitea token to that host and can be made to reach internal hosts. No fix is confirmed yet.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- github:DeepAudit affected >= 2.0.0-beta.5, <= 3.8.0 fixed no fixed version listed

## How to check

Check your DeepAudit version (backend image tag ghcr.io/lintsinghua/deepaudit-backend:<tag> or the release you deployed): 2.0.0-beta.5 through 3.8.0 is listed as affected. Then check whether GITLAB_TOKEN or GITEA_TOKEN is set in backend/.env or the container environment, and whether registered users other than you can create projects. Rotate any such token if untrusted users have accounts.

## Fix

No fixed version published in sources I could read; check github.com/lintsinghua/DeepAudit releases and the maintainer's tracker. Until then: remove the server-wide GITLAB_TOKEN/GITEA_TOKEN, or rotate it and use a least-privilege read-only token, and disable open registration.

## Timeline

- 2026-11-16T15:37:54+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-129880
- 2026-11-16T15:41:37+00:00 analyst https://vul.yulun.ac.cn/20261106/deepaudit/ — VulnCheck advisory read (CNA, not vendor): affected >= 2.0.0-beta.5 <= 3.8.0, CVSS v4 8.3, credit Wu Yulun. No fixed version found: maintainer releases page I could fetch lists only up to v3.0.4, no GHSA for this CVE, researcher page (linked) covers other DeepAudit bugs in the excerpt I read. Nothing verified.

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.5-through-3.8.0-ssrf-via-project-branch-listing-leaks-git-tokens
- [mentions] DeepAudit Vulnerability Report (Wu Yulun) https://vul.yulun.ac.cn/20261106/deepaudit/

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
