Skip to main content
Menu
CVEs

CVE

DeepAudit remote code execution via path traversal in upload-zip

CVE-2026-129879EUVD-2026-126441GHSA-9PQ5-G2HG-465C

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

8.7HighCNA
Exploited
Proof of concept public, per CISA
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affects DeepAudit 2.0.0-beta.1 to 3.0.4 according to the vendor-specific report. Repository type 'other' causes the server to git clone the attacker's repository, which preserves symlinks. The backend runs uvicorn with --reload, so the overwritten main.py is executed on reload.

Published
Last modified
Reference
Last checked
38/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: total

Summary

DeepAudit 2.0.0-beta.1 through 3.8.0 contains a path traversal vulnerability that allows authenticated users to write arbitrary files by importing projects with crafted IDs. Attackers can set absolute or ../ project IDs via /api/v1/database/import, then upload ZIPs through /api/v1/scan/upload-zip following cloned symlinks to overwrite app/main.py for remote code execution.

Who should check

Teams running DeepAudit 2.0.0-beta.1 to 3.0.4, including deployments that clone attacker-supplied Git repositories with repository_type other.

“Affected versions: 2.0.0-beta.1 to 3.0.4”

vul.yulun.ac.cn

cve.now Index

38Pcve.now Index 38 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.7/10CVSS 8.7, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 45 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Affects DeepAudit 2.0.0-beta.1 to 3.0.4 according to the vendor-specific report. Repository type 'other' causes the server to git clone the attacker's repository, which preserves symlinks. The backend runs uvicorn with --reload, so the overwritten main.py is executed on reload.
  • Workaround: The checked facts do not include a workaround or mitigation. The vendor's guidance for this issue is not in the checked facts.

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-129879 (DeepAudit 2.0.0-beta.1 through 3.8.0 Path Traversal via upload-zip Project ID), 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-129879 (entry last updated 2026-11-16):
Affected:
- lintsinghua DeepAudit: from 2.0.0-beta.1, through 3.8.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects DeepAudit 2.0.0-beta.1 to 3.0.4 according to the vendor-specific report. (source: https://vul.yulun.ac.cn/20261106/deepaudit/)
- Repository type 'other' causes the server to git clone the attacker's repository, which preserves symlinks. (source: https://vul.yulun.ac.cn/20261106/deepaudit/)
- The backend runs uvicorn with --reload, so the overwritten main.py is executed on reload. (source: https://vul.yulun.ac.cn/20261106/deepaudit/)
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-129879 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129879 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/services/zip_storage.py#L22-L48
- https://github.com/lintsinghua/DeepAudit/blob/9aa46568f20b2ab2dbc1878a4479392012c1230a/backend/app/api/v1/endpoints/scan.py#L230-L268
- https://github.com/lintsinghua/DeepAudit/blob/9aa46568f20b2ab2dbc1878a4479392012c1230a/backend/app/api/v1/endpoints/database.py#L202-L251
- https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.1-through-3.8.0-path-traversal-via-upload-zip-project-id
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-129879
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-129879"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • lintsinghua DeepAudit

    From 2.0.0-beta.1 · through 3.8.0

Evidence 7

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Repository
  2. Repository
  3. Repository
  4. Link
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129879

Is CVE-2026-129879 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A path traversal flaw in the upload-zip Project ID lets an attacker write files outside the intended location, overwriting app/main.py. Because the backend runs uvicorn with --reload, the overwritten file runs on reload, which can give remote code execution on the server and reach the host filesystem through the mounted Docker socket.Source: vul.yulun.ac.cn

Which versions are affected by CVE-2026-129879?

DeepAudit: from 2.0.0-beta.1 through 3.8.0.Source: cve.now feed data

Am I affected, and how do I check?

The product data lists DeepAudit 2.0.0-beta.1 through 3.8.0, while a vendor-specific report says 2.0.0-beta.1 to 3.0.4, so the exact range is not settled. The exposed setup involves repository type 'other', where the server git clones the repository and keeps its symlinks, and the official compose file, which runs uvicorn with --reload. Check your DeepAudit version and the repository type used for projects.Source: vul.yulun.ac.cn

How do I fix CVE-2026-129879?

The checked facts do not name a fixed version or vendor patch ids, so no upgrade target can be given from them. Check the vendor's advisory for an update that addresses this issue.Source: vul.yulun.ac.cn

What if there's no patch?

The checked facts do not include a workaround or mitigation. The vendor's guidance for this issue is not in the checked facts.Source: vul.yulun.ac.cn