CVE-2026-8177

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
7.5EG
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::LibXML versions through 2.0210 for Perl read out-of-bounds heap memory when parsing XML node names containing truncated UTF-8 byte sequences.

A node name ending in the middle of a multi byte UTF-8 sequence causes the parser to read past the end of the input string into adjacent heap memory.

Any Perl process that passes attacker controlled strings to XML::LibXML's DOM node-name methods can reach this path on the default API. The likely consequence is a crash, causing denial of service.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

May 10, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

oss-security - Re: CVE-2026-8177: XML::LibXML versions through 2.0210 for Perl read out-of-bounds heap memory when parsing XML node names containing truncated UTF-8 byte sequences

http://www.openwall.com/lists/oss-security/2026/05/11/2
generic

oss-security - CVE-2026-8177: XML::LibXML versions through 2.0210 for Perl read out-of-bounds heap memory when parsing XML node names containing truncated UTF-8 byte sequences

http://www.openwall.com/lists/oss-security/2026/05/10/8
generic

fix: validate UTF-8 continuation bytes in domParseChar by toddr-bot · Pull Request #149 · cpan-authors/XML-LibXML · GitHub

https://github.com/cpan-authors/XML-LibXML/pull/149
generic

Security: Out-of-bounds heap read in domParseChar on truncated UTF-8 sequences · Issue #146 · cpan-authors/XML-LibXML · GitHub

https://github.com/cpan-authors/XML-LibXML/issues/146

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatperl-XML-LibXML-1:2.0206-5.el9_4.12026-09-17redhat
redhatperl-XML-LibXML-1:2.0210-4.el10_0.12026-09-17redhat
redhatperl-XML-LibXML-1:2.0206-5.el9_2.12026-09-17redhat
redhatperl-XML-LibXML-1:2.0206-5.el9_6.12026-09-17redhat
redhatperl-XML-LibXML-1:2.0132-3.el8_102026-07-15redhat
redhatperl-XML-LibXML-1:2.0206-5.el9_8.12026-07-15redhat
redhatperl-XML-LibXML-1:2.0210-4.el10_2.12026-07-14redhat

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-libxml-perl2.0134+dfsg-2 ... 2.0207+dfsg-2 (12 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxml-libxml-perl2.0207+dfsg+really+2.0134-12.0207+dfsg+really+2.0134-1+deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxml-libxml-perl2.0207+dfsg+really+2.0134-52.0207+dfsg+really+2.0134-5+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxml-libxml-perl2.0207+dfsg+really+2.0134-5, 2.0207+dfsg+really+2.0134-6, 2.0207+dfsg+really+2.0134-72.0207+dfsg+really+2.0134-8

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 44× 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 268 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-8177?
CVE-2026-8177 is a high vulnerability published on May 10, 2026. XML::LibXML versions through 2.0210 for Perl read out-of-bounds heap memory when parsing XML node names containing truncated UTF-8 byte sequences. A node name ending in the middle of a multi byte UTF-8 sequence causes the parser to read past the end of the input string into adjacent heap memory.…
When was CVE-2026-8177 disclosed?
CVE-2026-8177 was first published in the National Vulnerability Database on May 10, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8177 actively exploited?
CVE-2026-8177 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 51.3% of all scored CVEs.
What is the CVSS score of CVE-2026-8177?
CVE-2026-8177 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-8177?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8177, 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-2026-8177

Explore →

Is Your Infrastructure Affected by CVE-2026-8177?

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