CVE-2025-11059 — xml2rfc
Fix: ietf-tools/xml2rfc@73fb1c9CVE-2025-11059 is a security vulnerability in xml2rfc. A fix is available for xml2rfc — see the affected versions and patch details below.
xml2rfc is vulnerable to arbitrary file reads through prepped files
Real-World Exposure
xml2rfcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
When generating PDF files, this vulnerability allows an attacker to read arbitrary files from the filesystem by injecting malicious link element into the prepped RFCXML.
Workarounds
Test untrusted input with link elements with rel="attachment" before processing.
References
This is related to GHSA-cfmv-h8fx-85m7.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | xml2rfc | all versions | 3.30.2pip install --upgrade 'xml2rfc==3.30.2' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xml2rfc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xml2rfc to 3.30.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-11059 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2025-11059 in your dependencies?
Find it across PyPI, including transitive dependencies.