CVE-2025-6170: libxml2: xmllint shell stack overflow causes local crash
LOWPoC AVAILABLECVE-2025-6170 is a stack buffer overflow in the interactive shell of libxml2's xmllint command-line tool, triggered when a user types an overly long command. It is a low-severity issue (CVSS 2.5) that needs local access, high attack complexity and user interaction, so it is not a realistic remote attack path against AI services. The package is widely embedded (95 downstream dependents) and appears in Red Hat container images such as RHAIIS vLLM CUDA/ROCm and RHAI base images, but the vulnerable tool is a developer utility that is rarely exposed in production inference paths. EPSS sits at the 77th percentile with a public PoC, yet the score itself is only 0.003, the CVE is not in CISA KEV and SSVC says TRACK, so there is no sign of active exploitation. Apply the Red Hat errata (for example RHSA-2026:36734) during normal patch cycles and rebuild affected container images, with no emergency response needed.
What is the risk?
Low overall risk. The attack requires local access, high complexity and user interaction, and the impact is limited to availability (a crash), with possible code execution only in rare configurations lacking stack protections. Exposure in AI/ML systems is incidental: libxml2 ships as a base-image dependency in vLLM and RHAI containers, but the vulnerable xmllint interactive shell is rarely run there. A public PoC exists, but there is no KEV listing and the EPSS probability is very low.
How does the attack unfold?
What systems are affected?
How severe is it?
What is the attack surface?
What should I do?
5 stepsApply the Red Hat errata (RHSA-2026:36734, 39304, 39317, 44481, 46836, 53371, 58981, 70596, 70639, 72394) that matches your image and rebuild or pull updated container images.
Inventory AI base images with an SBOM scan to find libxml2 and xmllint.
Remove xmllint from production images where it is not needed, or avoid its interactive shell mode.
Keep stack protection (stack canaries, ASLR, NX) enabled on hosts and containers.
Monitor for unexpected xmllint processes or crashes in container logs.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2025-6170?
CVE-2025-6170 is a stack buffer overflow in the interactive shell of libxml2's xmllint command-line tool, triggered when a user types an overly long command. It is a low-severity issue (CVSS 2.5) that needs local access, high attack complexity and user interaction, so it is not a realistic remote attack path against AI services. The package is widely embedded (95 downstream dependents) and appears in Red Hat container images such as RHAIIS vLLM CUDA/ROCm and RHAI base images, but the vulnerable tool is a developer utility that is rarely exposed in production inference paths. EPSS sits at the 77th percentile with a public PoC, yet the score itself is only 0.003, the CVE is not in CISA KEV and SSVC says TRACK, so there is no sign of active exploitation. Apply the Red Hat errata (for example RHSA-2026:36734) during normal patch cycles and rebuild affected container images, with no emergency response needed.
Is CVE-2025-6170 actively exploited?
Proof-of-concept exploit code is publicly available for CVE-2025-6170, increasing the risk of exploitation.
How to fix CVE-2025-6170?
1. Apply the Red Hat errata (RHSA-2026:36734, 39304, 39317, 44481, 46836, 53371, 58981, 70596, 70639, 72394) that matches your image and rebuild or pull updated container images. 2. Inventory AI base images with an SBOM scan to find libxml2 and xmllint. 3. Remove xmllint from production images where it is not needed, or avoid its interactive shell mode. 4. Keep stack protection (stack canaries, ASLR, NX) enabled on hosts and containers. 5. Monitor for unexpected xmllint processes or crashes in container logs.
What systems are affected by CVE-2025-6170?
This vulnerability affects the following AI/ML architecture patterns: model serving, container base images, training pipelines.
What is the CVSS score for CVE-2025-6170?
CVE-2025-6170 has a CVSS v3.1 base score of 2.5 (LOW). The EPSS exploitation probability is 0.34%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0010.001AI SoftwareAML.T0011User ExecutionCompliance Controls Affected
What are the technical details?
Original Advisory
A flaw was found in the interactive shell of the xmllint command-line tool, used for parsing XML files. When a user inputs an overly long command, the program does not check the input size properly, which can cause it to crash. This issue might allow attackers to run harmful code in rare configurations without modern protections.
Exploitation Scenario
An attacker with a foothold on a build or debugging host for an AI model-serving container persuades an engineer to open xmllint in interactive shell mode and paste an oversized command. The input overflows a stack buffer and crashes the process, interrupting the engineer's troubleshooting session. Code execution would require a hardened-protection-free build and extra effort. The attack is impractical against a running inference service.
Weaknesses (CWE)
CWE-121 — Stack-based Buffer Overflow: The product writes past the end of a buffer that was allocated on the stack.
- [Operation, Build and Compilation] Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- [Architecture and Design] Use an abstraction library to abstract away risky APIs. Not a complete solution.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:LReferences
- access.redhat.com/errata/RHSA-2026:36734vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:39304vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:39317vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:44481vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:46836vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:53371vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:58981vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:70596vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:70639vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72394vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72395vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72399vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72470vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72475vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72476vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72502vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73859vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73909vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73929vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73930vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73959vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73960vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73961vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73962vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74359vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74360vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74361vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74362vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74363vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74364vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74365vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74450vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74458vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74459vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74460vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74461vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74462vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74463vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74674vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74677vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74678vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74679vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74681vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74683vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74685vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74687vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74688vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74771vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:7519vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75652vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75654vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75655vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75657vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75658vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75659vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75660vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:76042vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:79118vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:79119vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:79120vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:79121vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:80756vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:81127vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82059vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82061vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82066vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82304vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82322vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82336vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82347vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82354vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82368vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82371vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82372vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82415vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82857vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82888vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:92449vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:92452vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:93473vendor-advisoryx_refsource_REDHAT
- access.redhat.com/security/cve/CVE-2025-6170vdb-entryx_refsource_REDHAT
- bugzilla.redhat.com/show_bug.cgiissue-trackingx_refsource_REDHAT
- gitlab.gnome.org/GNOME/libxml2/-/issues/941
- github.com/8-cm/kube-dumpExploit
- github.com/Lekssays/LekssaysExploit
- github.com/meyayl/docker-languagetoolExploit
- github.com/w4zu/Debian_securityExploit
Timeline
Related Vulnerabilities
CVE-2026-6173210.0Decepticon: ChatML token injection yields sandbox RCE
Same package: vllmCVE-2024-110419.8vllm: RCE via unsafe pickle deserialization in MessageQueue
Same package: vllmCVE-2026-259609.8vllm: SSRF allows internal network access
Same package: vllmCVE-2025-472779.8vLLM: RCE via exposed TCPStore in distributed inference
Same package: vllmCVE-2024-90539.8vllm: RCE via unsafe pickle deserialization in RPC server
Same package: vllm