Skip to main content
VulnerabilityPublished Updated

CVE-2026-8177: SHLOMIF XML::LibXML · Out-of-bounds Read

Affects SHLOMIF XML::LibXMLSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
SHLOMIFXML::LibXMLAffected
  • <=2.0210
Fixed in–
GitHubXML-LibXMLpkg:github/XML-LibXMLOther threatsAffected
  • <=2.0210
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released security updates for XML::LibXML in Red Hat Enterprise Linux 10 to address this vulnerability. Users should apply the official patches provided by Red Hat as detailed in their advisory (RHSA-2026:39547). Patch status is confirmed by the vendor advisory. No alternative mitigations or workarounds are specified.

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.

References

Community reviews

Loading reviews…