Application crash via character-byte count mismatch
Published Apr 8, 2025 · Updated Nov 3, 2025
Out-of-bounds memory access in XMLSoft libxml2 before 2.13.8 and 2.14.0 through 2.14.1 allows local users to crash applications. The xmlPythonFileRead and xmlPythonFileReadRaw callbacks return a Python character count where libxml2 expects a byte count, so multibyte UTF-8 text can exceed the caller-supplied buffer. Exploitation requires an application using the Python bindings to parse a character stream containing crafted multibyte text, and the demonstrated consequence is an application crash.
Summary
What happened
Out-of-bounds memory access in XMLSoft libxml2 before 2.13.8 and 2.14.0 through 2.14.1 allows local users to crash applications. The xmlPythonFileRead and xmlPythonFileReadRaw callbacks return a Python character count where libxml2 expects a byte count, so multibyte UTF-8 text can exceed the caller-supplied buffer. Exploitation requires an application using the Python bindings to parse a character stream containing crafted multibyte text, and the demonstrated consequence is an application crash.
The record
- CVE
- CVE-2025-32414
- Published
- Apr 8, 2025
- Updated
- Nov 3, 2025
- Vendor
- XMLSoft
- Product
- libxml2
- Classifications
- CWE-393, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.13.8
- Affected versionversion=2.14.0 <2.14.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream Unicode character-stream reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo