CVE-2026-8177

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
41.3%
KEV
Not listed

Published

May 10, 2026

Last Modified

July 15, 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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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 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-2026-8177 actively exploited?
CVE-2026-8177 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.