CVE-2026-11979 — libxml2
CVE-2026-11979 is a CWE-121 vulnerability. A fix is available — see the affected versions and patch details below.
Stack-Based Buffer Overflow in libxml2
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-11979.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Description
libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow internal buffers (command, arg, and argv) during input parsing. This results in memory corruption within the stack frame. Successful exploitation may cause a crash or potentially allow arbitrary code execution in the context of the xmlcatalog process.
This issue has been fixed in the commit c2e233fc.
NOTE: The maintainers of this project did not agree that this issue is a vulnerability and considered it a bug.
Affected Products
libxml2xmlsoftDetection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for CVE-2026-11979, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This Moderate impact flaw in libxml2 affects the `xmlcatalog` utility when operating in `--shell` mode. Exploitation requires an attacker to provide specially crafted, excessively long input, leading to stack-based buffer overflows. This vulnerability is limited to scenarios where an attacker can control input to the…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2026-11979 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | libxml2-0:2.12.5-10.el10_2.3 | RHSA-2026:60394 |
| Red Hat Enterprise Linux 8 | libxml2-0:2.9.7-21.el8_10.7 | RHSA-2026:61248 |
| Red Hat Enterprise Linux 9 | libxml2-0:2.9.13-14.el9_8.4 | RHSA-2026:61247 |
| Cert Manager support for Red Hat OpenShift release 1.20 | cert-manager/jetstack-cert-manager-rhel9:1790223279 | RHSA-2026:72394 |
| Cert Manager support for Red Hat OpenShift release 1.20 | cert-manager/cert-manager-istio-csr-rhel9:1790223719 | RHSA-2026:72395 |
| Cert Manager support for Red Hat OpenShift release 1.20 | cert-manager/cert-manager-operator-rhel9:1790272426 | RHSA-2026:72399 |
| Cert Manager support for Red Hat OpenShift release 1.20 | cert-manager/jetstack-cert-manager-acmesolver-rhel9:1790589998 | RHSA-2026:72470 |
| Cert Manager support for Red Hat OpenShift release 1.20 | cert-manager/cert-manager-istio-csr-rhel9:1790589914 | RHSA-2026:72475 |
Frequently Asked Questions
Is CVE-2026-11979 in your dependencies?
Find it across , including transitive dependencies.