CVE-2025-11059 json
xml2rfc is vulnerable to arbitrary file reads through prepped files
published 2025-09-10 13 mo ago modified 2026-07-07 4 mo ago also GHSA-9mv7-3c64-mmqw , PYSEC-2026-2057
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
### 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](https://github.com/ietf-tools/xml2rfc/security/advisories/GHSA-cfmv-h8fx-85m7).
Patch / fix
- pypi xml2rfc 3.30.2
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-11059 updated cvss 7.5
xml2rfc: xml2rfc is vulnerable to arbitrary file reads through prepped files
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | xml2rfc | <3.30.2 |
3.30.2 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/ietf-tools/xml2rfc/commit/73fb1c91fc62ac540bb6bd24f982f2becf84c1b0
web
-
github.com
/ietf-tools/xml2rfc/security/advisories/GHSA-9mv7-3c64-mmqw
web
-
github.com
/ietf-tools/xml2rfc
package
-
github.com
/ietf-tools/xml2rfc/releases/tag/v3.30.2
web
-
pypi.org
/project/xml2rfc
package
-
github.com
/advisories/GHSA-9mv7-3c64-mmqw
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-11059
advisory
Sources
- GitHub Advisory GHSA-9mv7-3c64-mmqw
- OSV PYSEC-2026-2057
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.