DEEPAUDIT · CVE-2026-129879 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
DeepAudit versions 2.0.0-beta.1 through 3.8.0 let an authenticated user import projects with crafted IDs that write files outside the intended directory. An attacker can overwrite app/main.py through symlinks and achieve remote code execution.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted DeepAudit instances in 2.0.0-beta.1 through 3.8.0 (VulnCheck) where someone can register or log in. The researcher's chain needs a regular account and a server that can reach an attacker-controlled Git repository. It then overwrites app/main.py through a symlink, and uvicorn --reload runs the new code. The official compose file mounts the Docker socket, so the researcher got host root. Instances reachable only by trusted users can skip it.
Not affected if no-untrusted-users, not-self-hosted, registration-closed, unauthenticated-only-access
Who cares deepaudit, docker, python, self-hosted
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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
2.0.0-beta.1 through 3.8.0 as affected; the maintainer's releases page I could read showed nothing newer than v3.0.4, which the researcher says is still affected