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.
Metrics
Affected Vendors & Products
References
History
Mon, 11 May 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
cvssV3_1
|
Mon, 11 May 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Shlomif
Shlomif xml::libxml |
|
| Vendors & Products |
Shlomif
Shlomif xml::libxml |
Mon, 11 May 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Mon, 11 May 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Sun, 10 May 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | 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 | |
| Weaknesses | CWE-125 | |
| References |
|
Status: PUBLISHED
Assigner: CPANSec
Published: 2026-05-10T20:48:51.816Z
Updated: 2026-05-11T16:53:25.716Z
Reserved: 2026-05-08T15:36:17.532Z
Link: CVE-2026-8177
Updated: 2026-05-11T16:53:25.716Z
Status : Received
Published: 2026-05-10T21:16:30.003
Modified: 2026-05-11T18:16:43.080
Link: CVE-2026-8177
No data.