# CVE-2026-8177: Memory corruption in XML::LibXML > Attacker can cause denial of service by triggering out-of-bounds heap reads in XML::LibXML via truncated UTF-8 node names. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 May 2026 - **Updated:** 18 Sep 2026 - **Also known as:** ALSA-2026:39547, ALSA-2026:39553, ALSA-2026:39878, AZL-86550, CLSA-2026-1784553427, CLSA-2026-1784554254, DEBIAN-CVE-2026-8177, ECHO-d531-9d26-ac4f, GHSA-g5h8-x64v-qf5h, MGASA-2026-0137, OESA-2026-3404, RHSA-2026:39547, RHSA-2026:39553, RHSA-2026:39878, RHSA-2026:68632, RHSA-2026:68685, RHSA-2026:68688, RHSA-2026:68693, RLSA-2026:39547, RLSA-2026:39553, RLSA-2026:39878, SUSE-SU-2026:22081-1, SUSE-SU-2026:2324-1, SUSE-SU-2026:2402-1, UBUNTU-CVE-2026-8177, openSUSE-SU-2026:10854-1, openSUSE-SU-2026:20908-1 ## What is CVE-2026-8177? CVE-2026-8177 is a high-severity memory corruption vulnerability in SHLOMIF XML::LibXML, published on 10 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2026-8177? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `perl-XML-LibXML` | AlmaLinux:10 | All versions | 1:2.0210-4.el10_2.1 | | `perl-XML-LibXML` | AlmaLinux:8 | All versions | 1:2.0132-3.el8_10 | | `perl-XML-LibXML` | AlmaLinux:9 | All versions | 1:2.0206-5.el9_8.1 | | `perl-XML-LibXML` | Red Hat:enterprise_linux:10.2 | All versions | 1:2.0210-4.el10_2.1 | | `perl-XML-LibXML-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 1:2.0210-4.el10_2.1 | | `perl-XML-LibXML-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 1:2.0210-4.el10_2.1 | | `perl-XML-LibXML` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.0132-3.el8_10 | | `perl-XML-LibXML-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.0132-3.el8_10 | | `perl-XML-LibXML-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.0132-3.el8_10 | | `perl-XML-LibXML` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.0206-5.el9_8.1 | | `perl-XML-LibXML-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.0206-5.el9_8.1 | | `perl-XML-LibXML-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.0206-5.el9_8.1 | | `perl-XML-LibXML` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:2.0210-4.el10_0.1 | | `perl-XML-LibXML` | Red Hat:rhel_e4s:9.2::appstream | All versions | 1:2.0206-5.el9_2.1 | | `perl-XML-LibXML` | Red Hat:rhel_e4s:9.4::appstream | All versions | 1:2.0206-5.el9_4.1 | | `perl-XML-LibXML` | Red Hat:rhel_eus:9.6::appstream | All versions | 1:2.0206-5.el9_6.1 | | `perl-XML-LibXML` | Rocky Linux:10 | All versions | 1:2.0210-4.el10_2.1 | | `perl-XML-LibXML` | Rocky Linux:8 | All versions | 1:2.0132-3.el8_10 | | `perl-XML-LibXML` | Rocky Linux:9 | All versions | 1:2.0206-5.el9_8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 2.0019-6.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.0210-160000.3.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.0019-6.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 2.0132-150000.3.8.1 | | `perl-XML-LibXML` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.0210-160000.3.1 | | `perl-XML-LibXML` | openSUSE:Leap 16.0 | All versions | 2.0210-160000.3.1 | | `perl-XML-LibXML` | openSUSE:Tumbleweed | All versions | 2.0212-1.1 | ## How do I fix CVE-2026-8177? Apply the vendor's patch. ## Is CVE-2026-8177 being exploited? There is no known exploitation of CVE-2026-8177 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-8177 and fix it if it is affected. What it is: CVE-2026-8177 is a high-severity memory corruption vulnerability in SHLOMIF XML::LibXML, published on 10 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-8177 in the wild and no public exploit code. Affected product: SHLOMIF XML::LibXML. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-8177/ (Markdown: https://insights.sbomify.com/CVE-2026-8177/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8177 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8177 - OSV: https://osv.dev/vulnerability/CVE-2026-8177 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-8177/ Summaries are generated and may contain mistakes; the official description above is the record.