How severe is CVE-2025-11058?

No CVSS score has been assigned to CVE-2025-11058 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-11058?

CVE-2025-11058 affects the following packages: xml2rfc (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2025-11058?

Update xml2rfc to 3.30.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-11058 is resolved across your whole dependency graph.

How do I detect CVE-2025-11058 in my PyPI dependencies?

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.

How do I mitigate CVE-2025-11058 if there is no patch (or I can't update yet)?

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.

Is CVE-2025-11058 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-11058 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2025-11058 published, and has it been updated?

CVE-2025-11058 was published on August 26, 2025 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2025-11058 — xml2rfc

Fix: ietf-tools/xml2rfc@f2b245b

CVE-2025-11058 is a security vulnerability in xml2rfc. A fix is available for xml2rfc — see the affected versions and patch details below.

xml2rfc has an arbitrary file read vulnerability

Also known asPYSEC-2026-2058

Published

Aug 26, 2025

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 7, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍xml2rfc

Real-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 XML.

Workarounds

Test untrusted input with link elements with rel="attachment" before processing.

Credits

This vulnerability was reported by Mohamed Ouad from Doyensec.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`xml2rfc`	all versions	3.30.1`pip install --upgrade 'xml2rfc==3.30.1'`

Detection & mitigation playbook

Open-source dependency

Detect
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.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-11058 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

### Impact When generating PDF files, this vulnerability allows an attacker to read arbitrary files from the filesystem by injecting malicious link element into the XML. ### Workarounds Test untrusted input with `link` elements with `rel="attachment"` before processing. ### Credits This vulnerability was reported by Mohamed Ouad from [Doyensec](https://doyensec.com/).

O3 Security · Impact-Aware SCA

Is CVE-2025-11058 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works