CVE
DeepAudit file read and SSRF in PDF report generator
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
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions 3.0.2 to 3.0.4 (per the vendor write-up) Project name is rendered into the PDF report subtitle without HTML escaping
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
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.
“Affected versions: 3.0.2 to 3.0.4”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions 3.0.2 to 3.0.4 (per the vendor write-up) Project name is rendered into the PDF report subtitle without HTML escapingWorkaround: 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.
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-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"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- lintsinghua DeepAudit
From 2.0.0-beta.1 · through 3.8.0
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129878
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: cve.now feed data
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: vul.yulun.ac.cn
Which versions are affected by CVE-2026-129878?
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 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: vul.yulun.ac.cn
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: vul.yulun.ac.cn
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: vul.yulun.ac.cn