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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-6170 is a low-severity libxml2 issue in xmllint's interactive shell. An overly long command can overflow a stack buffer and crash the tool. Sources describe code execution as possible only in rare configurations lacking modern protections, with local access and user interaction required.
Executive priority
Treat this as routine patch management, not an emergency. It can crash a local tool and has narrow exploitation conditions, but affected enterprise Linux and container platforms should still be updated through normal maintenance windows.
Technical view
The flaw is CWE-121 stack buffer overflow in xmllint command handling. CVSS 3.1 is 2.5: local attack vector, high complexity, no privileges, user interaction required, and availability impact only. Red Hat lists multiple supported platforms and packages as affected.
Likely exposure
Exposure is mainly systems where users or automation invoke xmllint interactive shell from affected libxml2 packages. Red Hat identifies RHEL 8, 9, 10, OpenShift Container Platform 4 rhcos, JBoss Core Services, and Hardened Images as affected; RHEL 6 and 7 status is unknown in the bundle.
Exploitation context
The source bundle does not show KEV listing or active exploitation. Practical exploitation appears constrained by local execution, required interaction, high complexity, and modern memory protections. The expected common impact is a crash of xmllint rather than broad remote compromise.
Researcher notes
Evidence supports a stack overflow in xmllint interactive command parsing, not a general XML parsing remote attack. Avoid overstating reach: exploitation requires local/user-interactive conditions. The bundle has vendor affected-state data, but limited fixed-version detail outside advisory references.
Mitigation direction
Apply vendor-provided libxml2 updates where Red Hat, Debian, or Siemens advisories apply.
Check vendor guidance for exact fixed package versions in your supported platform.
Limit xmllint interactive shell use with untrusted input until packages are updated.
Prioritize update tracking for affected Red Hat and OpenShift environments.
Validation and detection
Inventory installed libxml2 and xmllint package versions across Linux hosts and images.
Map findings to vendor affected-product statements, especially Red Hat package advisories.
Confirm whether automation exposes xmllint interactive shell to user-controlled commands.
Verify patched package deployment through your normal endpoint and image inventory tools.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.