CVE Tools
Track your stack

CVE-2025-6170

Libxml2: stack buffer overflow in xmllint interactive shell command handling

No known exploitation. EPSS puts it in the 25th percentile. Fixed versions are out.

CVSS 3.12.5LowEPSS percentile25th0.3% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products6 fixed builds listed below
Check it yourself

OpenVAS · 62 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.118781

Run the check

Published Updated Sources: CVE.org, NVD, BDU, CSAF

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Red Hat Enterprise Linux 10Fixed builds0:2.12.5-10.el10_2.2, 0:2.9.7-21.el8_10.6, 0:2.9.13-14.el9_8.2Stated by: CVE record
  • Red Hat Enterprise Linux 10.0 Extended Update SupportFixed builds0:2.12.5-9.el10_0.2Stated by: CVE record
  • Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update SupportFixed builds0:2.9.7-9.el8_4.20Stated by: CVE record
  • Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-OnFixed builds0:2.9.7-9.el8_4.20Stated by: CVE record
  • Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update SupportFixed builds0:2.9.7-13.el8_6.15Stated by: CVE record

Versions as the sources state them. 24 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS25th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 25th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

106 events over 508 days, from the signal feeds we watch.

  1. Patch availableworkaround available, record updated
  2. Patch availableworkaround available, record updated
  3. Patch availableworkaround available, record updated
  4. Patch availablepatch available, workaround available, workaround available, record updated, record updated
  5. Patch availableworkaround available, record updated
  6. Patch availableworkaround available, record updated

Affected products

And 30 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

Scored 2.5 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 239 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Jboss Core Services, not every advisory.