CVE-2006-10003

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-19. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 19, 2026

Last Modified

July 15, 2026

Advisory Details (9)

Auto-updated Oct 3, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7 Extended Lifecycle Support.

https://access.redhat.com/errata/RHSA-2026:8578
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions and Red Hat Enterprise Linux 8.8 Telecommunications Update Serv

https://access.redhat.com/errata/RHSA-2026:8577
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:7681
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:7680
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:7679
genericMentions a patch (unverified)

[SECURITY] [DLA 4522-1] libxml-parser-perl security update

https://lists.debian.org/debian-lts-announce/2026/04/msg00002.html
generic

oss-security - CVE-2006-10003: XML::Parser versions through 2.47 for Perl has an off-by-one heap buffer overflow in st_serial_stack

http://www.openwall.com/lists/oss-security/2026/03/19/2
generic

Buffer overflow in Expat.xs (patch) [rt.cpan.org #19860] · Issue #39 · cpan-authors/XML-Parser · GitHub

https://github.com/cpan-authors/XML-Parser/issues/39

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibxml-parser-perl (2.47-1ubuntu0.25.10.1) @ questing2026-06-12ubuntu
redhatperl-XML-Parser-0:2.46-9.el9_6.12026-04-22redhat
redhatperl-XML-Parser-0:2.46-9.el9_2.12026-04-21redhat
redhatperl-XML-Parser-0:2.46-9.el9_4.12026-04-21redhat
redhatperl-XML-Parser-0:2.46-9.el9_0.12026-04-21redhat
redhatperl-XML-Parser-0:2.47-6.el10_0.12026-04-20redhat
redhatperl-XML-Parser-0:2.44-11.el8_2.12026-04-16redhat
redhatperl-XML-Parser-0:2.44-11.el8_4.12026-04-16redhat
redhatperl-XML-Parser-0:2.41-10.el7_9.12026-04-16redhat
redhatperl-XML-Parser-0:2.44-11.el8_8.12026-04-16redhat
redhatperl-XML-Parser-0:2.44-11.el8_6.12026-04-16redhat
redhatperl-XML-Parser-0:2.44-12.el8_102026-04-13redhat
redhatperl-XML-Parser-0:2.47-6.1.el10_12026-04-13redhat
redhatperl-XML-Parser-0:2.46-9.1.el9_72026-04-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libxml-parser-perl2.46-2
  • every version up to 2.46-2+deb11u1: fixed in 2.46-2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libxml-parser-perl2.46-4
  • every version up to 2.46-4+deb12u1: fixed in 2.46-4+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libxml-parser-perl2.47-1
  • every version up to 2.47-2~deb13u1: fixed in 2.47-2~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libxml-parser-perl2.47-1, 2.47-2~deb13u1
  • every version up to 2.47-2: fixed in 2.47-2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 7× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 212 total refreshes for this CVE.

  1. 2026-10-09 19:59 UTCEPSS rescore
  2. 2026-10-08 16:32 UTCEPSS rescore
  3. 2026-10-07 23:36 UTCEPSS rescore
  4. 2026-10-06 15:08 UTCEPSS rescore
  5. 2026-10-05 17:37 UTCEPSS rescore
  6. 2026-10-04 23:15 UTCEPSS rescore
  7. 2026-10-03 14:19 UTCEPSS rescore
  8. 2026-09-29 02:58 UTCEG score recompute
  9. 2026-09-18 19:20 UTCEPSS rescore
  10. 2026-09-17 19:20 UTCEPSS rescore
  11. 2026-09-13 16:39 UTCEPSS rescore
  12. 2026-09-12 14:54 UTCEPSS rescore
  13. 2026-09-10 09:23 UTCEPSS rescore
  14. 2026-09-05 15:21 UTCEPSS rescore
  15. 2026-09-04 04:59 UTCEPSS rescore
  16. 2026-08-30 01:14 UTCEPSS rescore
  17. 2026-08-16 11:12 UTCEG score recompute
  18. 2026-08-16 11:12 UTCVendor advisory
  19. 2026-08-16 11:12 UTCGHSA enrichment
  20. 2026-08-14 23:46 UTCVendor advisory
  21. 2026-08-14 23:46 UTCGHSA enrichment
  22. 2026-08-14 19:54 UTCVendor advisory
  23. 2026-08-14 19:54 UTCGHSA enrichment
  24. 2026-08-14 15:05 UTCVendor advisory
  25. 2026-08-14 15:05 UTCGHSA enrichment
Show 75 more
  1. 2026-08-14 11:13 UTCVendor advisory
  2. 2026-08-14 11:13 UTCGHSA enrichment
  3. 2026-08-14 07:21 UTCEG score recompute
  4. 2026-08-14 07:21 UTCVendor advisory
  5. 2026-08-14 07:21 UTCGHSA enrichment
  6. 2026-08-13 01:58 UTCVendor advisory
  7. 2026-08-13 01:58 UTCGHSA enrichment
  8. 2026-08-12 22:06 UTCEG score recompute
  9. 2026-08-12 22:06 UTCVendor advisory
  10. 2026-08-12 22:06 UTCGHSA enrichment
  11. 2026-08-12 01:20 UTCVendor advisory
  12. 2026-08-12 01:20 UTCGHSA enrichment
  13. 2026-08-11 21:29 UTCEG score recompute
  14. 2026-08-11 21:29 UTCVendor advisory
  15. 2026-08-11 21:28 UTCGHSA enrichment
  16. 2026-08-11 08:36 UTCVendor advisory
  17. 2026-08-11 08:36 UTCGHSA enrichment
  18. 2026-08-11 04:32 UTCEG score recompute
  19. 2026-08-11 04:32 UTCVendor advisory
  20. 2026-08-11 04:32 UTCGHSA enrichment
  21. 2026-08-10 12:53 UTCVendor advisory
  22. 2026-08-10 12:53 UTCGHSA enrichment
  23. 2026-08-10 08:44 UTCVendor advisory
  24. 2026-08-10 08:44 UTCGHSA enrichment
  25. 2026-08-10 04:52 UTCVendor advisory
  26. 2026-08-10 04:52 UTCGHSA enrichment
  27. 2026-08-10 00:59 UTCVendor advisory
  28. 2026-08-10 00:59 UTCGHSA enrichment
  29. 2026-08-09 21:06 UTCVendor advisory
  30. 2026-08-09 21:06 UTCGHSA enrichment
  31. 2026-08-09 17:14 UTCEG score recompute
  32. 2026-08-09 17:14 UTCVendor advisory
  33. 2026-08-09 17:14 UTCGHSA enrichment
  34. 2026-08-09 13:23 UTCVendor advisory
  35. 2026-08-09 13:22 UTCGHSA enrichment
  36. 2026-08-09 06:55 UTCEG score recompute
  37. 2026-08-09 06:55 UTCVendor advisory
  38. 2026-08-09 06:55 UTCGHSA enrichment
  39. 2026-08-08 16:30 UTCEPSS rescore
  40. 2026-08-08 08:53 UTCVendor advisory
  41. 2026-08-08 08:53 UTCGHSA enrichment
  42. 2026-08-08 05:01 UTCVendor advisory
  43. 2026-08-08 05:01 UTCGHSA enrichment
  44. 2026-08-08 01:09 UTCVendor advisory
  45. 2026-08-08 01:09 UTCGHSA enrichment
  46. 2026-08-07 21:17 UTCVendor advisory
  47. 2026-08-07 21:17 UTCGHSA enrichment
  48. 2026-08-07 17:24 UTCEG score recompute
  49. 2026-08-07 17:24 UTCVendor advisory
  50. 2026-08-07 17:24 UTCGHSA enrichment
  51. 2026-08-06 19:27 UTCEG score recompute
  52. 2026-08-06 19:27 UTCVendor advisory
  53. 2026-08-06 19:27 UTCGHSA enrichment
  54. 2026-08-06 09:22 UTCVendor advisory
  55. 2026-08-06 09:22 UTCGHSA enrichment
  56. 2026-08-06 05:27 UTCVendor advisory
  57. 2026-08-06 05:27 UTCGHSA enrichment
  58. 2026-08-06 01:35 UTCEG score recompute
  59. 2026-08-06 01:35 UTCVendor advisory
  60. 2026-08-06 01:35 UTCGHSA enrichment
  61. 2026-08-05 19:11 UTCEPSS rescore
  62. 2026-08-04 15:03 UTCEPSS rescore
  63. 2026-08-04 04:35 UTCVendor advisory
  64. 2026-08-04 04:35 UTCGHSA enrichment
  65. 2026-08-04 00:43 UTCEG score recompute
  66. 2026-08-04 00:43 UTCVendor advisory
  67. 2026-08-04 00:43 UTCGHSA enrichment
  68. 2026-08-03 10:27 UTCEPSS rescore
  69. 2026-08-03 01:11 UTCVendor advisory
  70. 2026-08-03 01:11 UTCGHSA enrichment
  71. 2026-08-02 20:28 UTCVendor advisory
  72. 2026-08-02 20:28 UTCGHSA enrichment
  73. 2026-08-02 16:36 UTCEG score recompute
  74. 2026-08-02 16:36 UTCVendor advisory
  75. 2026-08-02 16:36 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2006-10003?
CVE-2006-10003 is a critical vulnerability published on March 19, 2026. XML::Parser versions through 2.47 for Perl has an off-by-one heap buffer overflow in stserialstack. 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…
When was CVE-2006-10003 disclosed?
CVE-2006-10003 was first published on March 19, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-10003 actively exploited?
CVE-2006-10003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2006-10003?
CVE-2006-10003 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2006-10003?
A fix for CVE-2006-10003 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2006-10003 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2006-10003

Explore →

Is Your Infrastructure Affected by CVE-2006-10003?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.