DeepAudit: an open endpoint hands over the audit platform's LLM and Git keys
DeepAudit's unauthenticated config endpoint returns the LLM and source-control credentials its audit agents run on.
· VulnCheck · Research by Wu Yulun
DeepAudit, an open-source AI code auditing platform, answers an unauthenticated GET on /api/v1/config/defaults with the operator's LLM API keys and GitHub or GitLab tokens. VulnCheck published four CVEs on November 16 and lists no fix.
- vulncheck.comVulnCheck Advisory
- github.comGitHub Advisory
- vul.yulun.ac.cnResearcher's Report
- +2 sources
01What happened
VulnCheck published four high-severity CVEs for DeepAudit on November 16, 2026, crediting Wu Yulun. DeepAudit is an open-source platform whose README describes a team of LLM agents that scan a project, write proof-of-concept scripts and verify them in a Docker sandbox, so it holds the operator's model and repository credentials. No fixed version is listed.
02How it works
A plain GET to /api/v1/config/defaults in DeepAudit's backend requires no authentication and returns the stored LLM provider API keys and GitHub or GitLab tokens. Wu Yulun's report describes three further issues in the same codebase, each with its own CVE below. One of them leaks the global GitLab or Gitea token, because the server accepts an arbitrary repository host and sends the token there when it fetches branches.
03Who is affected
Versions 2.0.0-beta.1 through 3.8.0 are affected, per VulnCheck's advisory. Exposure depends on who can reach the backend API, which the project's quick start brings up with Docker Compose alongside the web interface on port 3000. VulnCheck scores the confidentiality impact high and the integrity and availability impact none.
04What to do
Keep DeepAudit's backend off untrusted networks and put authentication in front of it, since no patched release exists. Rotate the LLM provider API keys and the GitHub, GitLab or Gitea tokens stored in the platform, then review what those repository tokens could reach.
Questions people ask
- Is there a patched version of DeepAudit?
- No fixed DeepAudit release is listed. VulnCheck's advisory for CVE-2026-129877 gives no patched version, and the project's releases page shows v3.0.4 as its latest tagged release. Until a fix ships, treat every credential stored in a reachable DeepAudit install as exposed, and keep the backend API off networks you do not control.
- What data does the DeepAudit config endpoint expose?
- An unauthenticated GET to /api/v1/config/defaults returns the operator's LLM provider API keys and GitHub or GitLab tokens, according to VulnCheck. Attackers can then spend against those model accounts and reach whatever repositories the tokens unlock. VulnCheck classes the flaw as CWE-306, missing authentication for a critical function, and scores it 8.7 under CVSS 4.0.
- How many DeepAudit flaws were published on November 16, 2026?
- Four DeepAudit CVEs appeared on November 16, 2026: CVE-2026-129877 for the unauthenticated config endpoint, CVE-2026-129878 for HTML injection in ReportGenerator, CVE-2026-129879 for path traversal and CVE-2026-129880 for server-side request forgery. GitHub's advisory database rates all four high and currently lists them as unreviewed.
- Which DeepAudit version am I running?
- VulnCheck lists DeepAudit 2.0.0-beta.1 through 3.8.0 as affected by CVE-2026-129877, while Wu Yulun's report describes the same four issues against versions up to 3.0.4, matching the newest release tag on the project's releases page. Check the running container image rather than the README, because the documented quick start pulls a published Docker Compose file.
Sources 5 links, all fetched
- 1vulncheck.comVulnCheck Advisory
- 2github.comGitHub Advisory
- 3vul.yulun.ac.cnResearcher's Report
- 4github.comPath Traversal CVE
- 5github.comDeepAudit Repository