← All advisories
CVE-2026-129879highCode execution2026-11-16

DeepAudit: project-ID path traversal to RCE (CVE-2026-129879), PDF-report file read/SSRF (CVE-2026-129878) and Git token leak via repository URL (CVE-2026-129880)

The three other DeepAudit issues from the 6 November vul.yulun.ac.cn report now have CVEs (NVD, 16 November 2026). Any registered user of the self-hosted AI code-audit platform can overwrite backend code for remote code execution through a crafted project ID, read server files or reach internal hosts through a project name rendered into the PDF report, and capture the server-wide GitLab or Gitea token by pointing a project at their own host. NVD lists versions up to 3.8.0 and no fixed release.

01.

What it is

CVE-2026-129879 (2.0.0-beta.1 through 3.8.0): /api/v1/database/import accepts any string as Project.id, and /api/v1/scan/upload-zip writes <project_id>.zip without validation. An absolute or ../ ID plus a symlink from an attacker repo cloned by an agent task lets the upload overwrite app/main.py; the official compose runs uvicorn --reload, so the new code runs. That backend also mounts the host Docker socket.

CVE-2026-129878 (2.0.0-beta.1 through 3.8.0 per NVD; the researchers list 3.0.2-3.0.4): ReportGenerator.generate_task_report puts the project name into the PDF subtitle without escaping, so an HTML link/attachment element in a project name makes the PDF renderer embed local files or internal URLs in the downloaded report.

CVE-2026-129880 (2.0.0-beta.5 through 3.8.0): when listing branches for a gitlab or gitea project, the server sends its global GitLab/Gitea token to whatever host repository_url names, so an attacker host receives the operator's token; the same request can probe internal hosts.

All three need only a normal registered account. The researchers' report gives narrower version ranges (introduced in 2.0.0-beta.1, 3.0.2 and 3.0.3 respectively) tested up to 3.0.4; the CVE records cover up to 3.8.0.

02.

How to check

  1. If you run DeepAudit 3.8.0 or earlier, assume all three apply; check whether self-registration is open and who has accounts.
  2. Inspect the database for projects whose id is not a UUID (contains / or ..) and for project names containing HTML tags.
03.

How to fix

  1. Keep DeepAudit off the internet and close open registration; only trusted users should have accounts.
  2. Don't mount /var/run/docker.sock into the backend and don't run it with uvicorn --reload in production.
  3. Rotate the server-side GitLab/Gitea (and GitHub and LLM) tokens on any instance where untrusted users had accounts, and watch the repository for a release that fixes these CVEs.
# run in your DeepAudit checkout: flags the risky defaults used by the official compose
docker compose config | grep -nE "docker.sock|--reload"
04.

Sources

Related on VibeVulns
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.