Memory corruption via off-by-one stack growth check
Published Mar 19, 2026 · Updated Mar 19, 2026
Heap buffer overflow in Todd Rinaldo XML::Parser 2.47 and earlier allows attackers to corrupt memory via deeply nested XML. The startElement routine in Expat/Expat.xs checks the current index instead of the next pre-incremented index, so st_serial_stack is not grown before a four-byte write past its allocation. The hosting process must parse attacker-controlled XML; a successful trigger can crash that process, while public evidence does not demonstrate code execution.
Summary
What happened
Heap buffer overflow in Todd Rinaldo XML::Parser 2.47 and earlier allows attackers to corrupt memory via deeply nested XML. The startElement routine in Expat/Expat.xs checks the current index instead of the next pre-incremented index, so st_serial_stack is not grown before a four-byte write past its allocation. The hosting process must parse attacker-controlled XML; a successful trigger can crash that process, while public evidence does not demonstrate code execution.
The record
- CVE
- CVE-2006-10003
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- Todd Rinaldo
- Product
- XML::Parser
- Classifications
- CWE-193, CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 19, 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.47
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
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