Memory corruption via split qualified-name bounds checks
Published Feb 18, 2025 · Updated Feb 26, 2026
Stack-based buffer overflow in XMLSoft libxml2 before 2.12.10 and 2.13.0 through 2.13.5 allows attackers to overwrite stack memory. In valid.c, xmlSnprintfElements separately checks namespace-prefix and element-name lengths against the same pre-append length, then concatenates both into a fixed stack buffer. Reachability requires DTD validation of an untrusted XML document or DTD; the overwrite corrupts the validating process's stack.
Summary
What happened
Stack-based buffer overflow in XMLSoft libxml2 before 2.12.10 and 2.13.0 through 2.13.5 allows attackers to overwrite stack memory. In valid.c, xmlSnprintfElements separately checks namespace-prefix and element-name lengths against the same pre-append length, then concatenates both into a fixed stack buffer. Reachability requires DTD validation of an untrusted XML document or DTD; the overwrite corrupts the validating process's stack.
The record
- CVE
- CVE-2025-24928
- Published
- Feb 18, 2025
- Updated
- Feb 26, 2026
- Vendor
- XMLSoft
- Product
- libxml2
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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.12.10
- Affected versionversion=2.13.0 <2.13.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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