CVE-2006-10003
Toddr Xml::parser buffer overflow
- Published19 Mar 2026
Description
XML::Parser versions through 2.47 for Perl has an off-by-one heap buffer overflow in st_serial_stack. In the case (stackptr == stacksize - 1), the stack will NOT be expanded. Then the new value will be written at location (++stackptr), which equals stacksize and therefore falls just outside the allocated buffer. The bug can be observed when parsing an XML file with very deep element nesting
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:7679
- https://access.redhat.com/errata/RHSA-2026:7680
- https://access.redhat.com/errata/RHSA-2026:7681
- https://access.redhat.com/errata/RHSA-2026:8577
- https://access.redhat.com/errata/RHSA-2026:8578
- https://access.redhat.com/errata/RHSA-2026:8608
- https://access.redhat.com/errata/RHSA-2026:8609
- https://access.redhat.com/errata/RHSA-2026:8610
- https://access.redhat.com/errata/RHSA-2026:9110
- https://access.redhat.com/errata/RHSA-2026:9246
and 11 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2006-10003 being actively exploited?
CVE-2006-10003 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.55%.
How severe is CVE-2006-10003?
CVE-2006-10003 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.55% probability of exploitation.
Which products are affected by CVE-2006-10003?
Affected products include Toddr Xml::parser.
How do I fix CVE-2006-10003?
Upgrade affected software to a fixed version, for example Toddr Xml::parser 2.48 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2006-10003 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.