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.

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::LibXMLs DOM node-name methods can reach this path on the default API. The likely consequence is a crash, causing denial of service.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name	Vendor	Start Version	End Version
Red Hat Enterprise Linux 10	RedHat	perl-XML-LibXML-1:2.0210-4.el10_2.1	*
Red Hat Enterprise Linux 10.0 Extended Update Support	RedHat	perl-XML-LibXML-1:2.0210-4.el10_0.1	*
Red Hat Enterprise Linux 8	RedHat	perl-XML-LibXML-1:2.0132-3.el8_10	*
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support	RedHat	perl-XML-LibXML-1:2.0132-2.el8_6.1	*
Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On	RedHat	perl-XML-LibXML-1:2.0132-2.el8_6.1	*
Red Hat Enterprise Linux 8.8 Telecommunications Update Service	RedHat	perl-XML-LibXML-1:2.0132-2.el8_8.1	*
Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions	RedHat	perl-XML-LibXML-1:2.0132-2.el8_8.1	*
Red Hat Enterprise Linux 9	RedHat	perl-XML-LibXML-1:2.0206-5.el9_8.1	*
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions	RedHat	perl-XML-LibXML-1:2.0206-5.el9_2.1	*
Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions	RedHat	perl-XML-LibXML-1:2.0206-5.el9_4.1	*
Red Hat Enterprise Linux 9.6 Extended Update Support	RedHat	perl-XML-LibXML-1:2.0206-5.el9_6.1	*
Libxml-libxml-perl	Ubuntu	questing	*
Libxml-libxml-perl	Ubuntu	upstream	*

Potential Mitigations

Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

https://cwe.mitre.org/data/definitions/540.html

NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-8177
CWE	https://cwe.mitre.org/data/definitions/125.html

Out-of-bounds Read

Weakness

Affected Software

Potential Mitigations

References

CVE-2026-8177

Out-of-bounds Read

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References