Skip to main content
Menu
CVEs

CVE

DeepAudit information disclosure in unauthenticated config endpoint

DeepAudit versions 2.0.0-beta.1 through 3.8.0 expose server secrets through /api/v1/config/defaults without authentication. CVSS rates it 8.7 High. The checked facts name no fixed version.

CVE-2026-129877EUVD-2026-126443

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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

8.7HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: The checked facts do not describe a workaround. Until a fix is confirmed, limiting access to the /api/v1/config/defaults endpoint is the only step the facts point toward, and they do not say how to do that.

Published
Last modified
Reference
Last checked
34/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

DeepAudit 2.0.0-beta.1 through 3.8.0 contains an information disclosure vulnerability that allows unauthenticated attackers to retrieve server secrets through the /api/v1/config/defaults endpoint. Attackers can send a GET request to obtain the operator's LLM provider API keys and GitHub or GitLab tokens, then abuse those services and accessible repositories.

Who should check

Teams running DeepAudit 2.0.0-beta.1 through 3.8.0 (lintsinghua) that have LLM provider API keys or GitHub/GitLab tokens configured on the server.

“Affecting DeepAudit >= 2.0.0-beta.1, <= 3.8.0”

vulncheck.com

cve.now Index

34Pcve.now Index 34 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 79 if added to CISA KEV
  • Would score about 74 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts do not describe a workaround. Until a fix is confirmed, limiting access to the /api/v1/config/defaults endpoint is the only step the facts point toward, and they do not say how to do that.

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-129877 (DeepAudit 2.0.0-beta.1 through 3.8.0 Information Disclosure via /api/v1/config/defaults), 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-129877 (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):
- Affected versions are DeepAudit 2.0.0-beta.1 through 3.8.0. (source: https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.1-through-3.8.0-information-disclosure-via-api-v1-config-defaults)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129877 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129877 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/api/v1/endpoints/config.py#L109-L154
- https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.1-through-3.8.0-information-disclosure-via-api-v1-config-defaults
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-129877
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-129877"}.

Timeline

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

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • lintsinghua DeepAudit

    From 2.0.0-beta.1 · through 3.8.0

Evidence 5

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Link
  3. Link

Corrections

None so far.

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

Questions about CVE-2026-129877

Is CVE-2026-129877 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. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The flaw lets an unauthenticated party retrieve server secrets from the /api/v1/config/defaults endpoint. The secrets include the operator's LLM provider API keys and GitHub or GitLab tokens, which could then be used against those services and the repositories they can access.Source: vulncheck.com

Which versions are affected by CVE-2026-129877?

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 affected range is DeepAudit 2.0.0-beta.1 through 3.8.0. The version can be checked in the DeepAudit installation, and the checked facts do not describe any configuration that changes whether the endpoint is exposed.Source: vulncheck.com

How do I fix CVE-2026-129877?

The checked facts do not name a fixed version or vendor patch identifiers, so no upgrade target can be stated from them. Check the DeepAudit advisory or vendor channels for a fix.Source: vulncheck.com

What if there's no patch?

The checked facts do not describe a workaround. Until a fix is confirmed, limiting access to the /api/v1/config/defaults endpoint is the only step the facts point toward, and they do not say how to do that.Source: vulncheck.com