CVE-2025-6170: libxml2: xmllint shell stack overflow causes local crash

LOWPoC AVAILABLE
Published June 16, 2025
CISO Take

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.

Sources:NVDEPSSATLASaccess.redhat.com

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?

Initial Access
Attacker gains local access or convinces an engineer to run xmllint interactively inside an AI container or build host.
AML.T0011
Exploitation
An overly long command entered in the xmllint shell overflows a stack buffer.
Impact
The xmllint process crashes, causing local denial of service, with code execution only in rare unprotected configurations.

What systems are affected?

PackageEcosystemVulnerable RangePatched
vLLMpip—No patch
96.9K93 dependentsPushed 3d ago26% patched~37d to patchFull package profile →
vLLMpip—No patch
96.9K93 dependentsPushed 3d ago26% patched~37d to patchFull package profile →
vLLMpip—No patch
96.9K93 dependentsPushed 3d ago26% patched~37d to patchFull package profile →
cert-manager/cert-manager-istio-csr-rhel9——No patch
cert-manager/cert-manager-operator-rhel9——No patch
cert-manager/cert-manager-trust-manager-rhel9——No patch
cert-manager/jetstack-cert-manager-acmesolver-rhel9——No patch
cert-manager/jetstack-cert-manager-rhel9——No patch
discovery/discovery-server-rhel9——No patch
discovery/discovery-ui-rhel9——No patch
insights-proxy/insights-proxy-container-rhel9——No patch
libxml2——No patch
libxml2-main——No patch
openshift/ose-rhel-coreos-8——No patch
openshift/ose-rhel-coreos-9——No patch
rhai/base-image-cpu-rhel9——No patch
rhai/base-image-rocm-rhel9——No patch
rhai/base-image-spyre-rhel9——No patch
rhai/base-image-tpu-rhel9——No patch
rhaiis/model-opt-cuda-rhel9——No patch
rhui5/cds-kubernetes-rhel9——No patch
rhui5/cds-kubernetes-tp-rhel9——No patch
rhui5/cds-rhel9——No patch
rhui5/haproxy-rhel9——No patch
rhui5/installer-rhel9——No patch
rhui5/installer-tp-rhel9——No patch
rhui5/rhua-rhel9——No patch
rhui5/rhua-tp-rhel9——No patch

How severe is it?

CVSS 3.1
2.5 / 10
EPSS
0.3%
chance of exploitation in 30 days
Higher than 27% of all CVEs
Exploitation Status
Exploit Available
Exploitation: MEDIUM
Sophistication
Advanced
Exploitation Confidence
medium
○Public PoC indexed (trickest/cve)
Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

What is the attack surface?

AVACPRUISCIA
AVLocal
ACHigh
PRNone
UIRequired
SUnchanged
CNone
INone
ALow

What should I do?

5 steps
  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 does CISA's SSVC say?

DecisionTrack
Exploitationnone
AutomatableNo
Technical Impactpartial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

DoSCode ExecutionInferenceFrameworkAML.T0010.001AML.T0011

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
MANAGE 2.3-Response to previously unknown risks and supply chain risk management
OWASP LLM Top 10
LLM03-Supply Chain

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

model servingcontainer base imagestraining pipelines

MITRE ATLAS Techniques

AML.T0010.001AI Software
AML.T0011User Execution

Compliance Controls Affected

ISO 42001: A.6.2.6
NIST AI RMF: MANAGE 2.3
OWASP LLM Top 10: LLM03

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:L

References

Timeline

Published
June 16, 2025
Last Modified
November 6, 2026
First Seen
September 30, 2026

Related Vulnerabilities