CVE-2006-10002

CRITICALNVD 7.59.8
EchelonGraph scoreMEDIUM confidence

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

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: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

XML::Parser versions through 2.45 for Perl could overflow the pre-allocated buffer size cause a heap corruption (double free or corruption) and crashes.

A :utf8 PerlIO layer, parse_stream() in Expat.xs could overflow the XML input buffer because Perl's read() returns decoded characters while SvPV() gives back multi-byte UTF-8 bytes that can exceed the pre-allocated buffer size. This can cause heap corruption (double free or corruption) and crashes.

CVSS v3
7.5
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

March 19, 2026

Last Modified

June 16, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

XML::Parser::Expat crashes on utf8 stream [rt.cpan.org #19859] · Issue #64 · cpan-authors/XML-Parser · GitHub

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

Vendor Advisories for CVE-2006-10002(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
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_0.12026-04-21redhat
redhatperl-XML-Parser-0:2.46-9.el9_4.12026-04-21redhat
redhatperl-XML-Parser-0:2.47-6.el10_0.12026-04-20redhat
redhatperl-XML-Parser-0:2.44-11.el8_6.12026-04-16redhat
redhatperl-XML-Parser-0:2.44-11.el8_8.12026-04-16redhat
redhatperl-XML-Parser-0:2.44-11.el8_4.12026-04-16redhat
redhatperl-XML-Parser-0:2.44-11.el8_2.12026-04-16redhat
redhatperl-XML-Parser-0:2.41-10.el7_9.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 rangeFixed inDependents
libxml-parser-perl2.46-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxml-parser-perl2.46-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxml-parser-perl2.46-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxml-parser-perl2.46-1

Weakness Classification(2)

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

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 2× in last 7d / 23× 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.

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

Frequently asked(5)

What is CVE-2006-10002?
CVE-2006-10002 is a critical vulnerability published on March 19, 2026. XML::Parser versions through 2.45 for Perl could overflow the pre-allocated buffer size cause a heap corruption (double free or corruption) and crashes. A :utf8 PerlIO layer, parse_stream() in Expat.xs could overflow the XML input buffer because Perl's read() returns decoded characters while SvPV()…
When was CVE-2006-10002 disclosed?
CVE-2006-10002 was first published in the National Vulnerability Database on March 19, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-10002 actively exploited?
CVE-2006-10002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.0% of all scored CVEs.
What is the CVSS score of CVE-2006-10002?
CVE-2006-10002 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8.
How do I remediate CVE-2006-10002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-10002, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2006-10002?

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