Skip to content
Noroxi
NVD / CVE Program· CNA canonical

CVE-2025-9714: Stack overflow in libxml2

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: libxml2 libxml2 2.10.0, 2.12.7+dfsg+really2.9.14-0.4ubuntu0.3, 2.9.1+dfsg1-3ubuntu4.13+esm9.

Low priority for now. Upgrade to libxml2 libxml2 2.10.0, 2.12.7+dfsg+really2.9.14-0.4ubuntu0.3, 2.9.1+dfsg1-3ubuntu4.13+esm9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Uncontrolled recursion in XPath evaluation in libxml2 up to and including version 2.9.14 allows a local attacker to cause a stack overflow via crafted expressions. XPath processing functions `xmlXPathRunEval`, `xmlXPathCtxtCompile`, and `xmlXPathEvalExpr` were resetting recursion depth to zero before making potentially recursive calls. When such functions were called recursively this could allow for uncontrolled recursion and lead to a stack overflow. These functions now preserve recursion depth across recursive calls, allowing recursion depth to be controlled.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 10, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · canonical
6.2
0.7 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-9714

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for xmlsoft records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
xmlsoftlibxml2

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • xmlsoft libxml2before 2.10.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (canonical). Independent of NVD's CPE analysis and usually ahead of it.

  • libxml2 libxml2

    • before 2.10.0affected · semver
    • before 2.12.7+dfsg+really2.9.14-0.4ubuntu0.3affected · dpkg
    • before 2.9.14+dfsg-1.3ubuntu3.5affected · dpkg
    • before 2.9.13+dfsg-1ubuntu0.9affected · dpkg
    • before 2.9.10+dfsg-5ubuntu0.20.04.10+esm2affected · dpkg
    • before 2.9.4+dfsg1-6.1ubuntu1.9+esm5affected · dpkg
    • before 2.9.3+dfsg1-1ubuntu0.7+esm10affected · dpkg
    • before 2.9.1+dfsg1-3ubuntu4.13+esm9affected · dpkg

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8libxml2before 2.9.7-21.el8_10.82.9.7-21.el8_10.8
AlmaLinux:8libxml2before 2.9.7-21.el8_10.42.9.7-21.el8_10.4
AlmaLinux:8libxml2-develbefore 2.9.7-21.el8_10.42.9.7-21.el8_10.4
AlmaLinux:8libxml2-develbefore 2.9.7-21.el8_10.82.9.7-21.el8_10.8
AlmaLinux:8python3-libxml2before 2.9.7-21.el8_10.82.9.7-21.el8_10.8
AlmaLinux:8python3-libxml2before 2.9.7-21.el8_10.42.9.7-21.el8_10.4
AlmaLinux:9libxml2before 2.9.13-14.el9_72.9.13-14.el9_7
AlmaLinux:9libxml2-develbefore 2.9.13-14.el9_72.9.13-14.el9_7
AlmaLinux:9python3-libxml2before 2.9.13-14.el9_72.9.13-14.el9_7
Debian:11libxml2before 2.9.10+dfsg-6.7+deb11u92.9.10+dfsg-6.7+deb11u9
Debian:12libxml2before 2.9.14+dfsg-1.3~deb12u52.9.14+dfsg-1.3~deb12u5
Debian:13libxml2before 2.12.7+dfsg+really2.9.14-2.1+deb13u22.12.7+dfsg+really2.9.14-2.1+deb13u2
Debian:14libxml2before 2.14.5+dfsg-0.12.14.5+dfsg-0.1
openSUSE:Leap 15.6python-libxml2-pythonbefore 2.9.7-150000.3.88.12.9.7-150000.3.88.1
Red Hat:enterprise_linux:8::appstreamlibxml2-debuginfobefore 0:2.9.7-21.el8_10.40:2.9.7-21.el8_10.4
Red Hat:enterprise_linux:8::appstreamlibxml2-debugsourcebefore 0:2.9.7-21.el8_10.40:2.9.7-21.el8_10.4
Red Hat:enterprise_linux:8::appstreamlibxml2-develbefore 0:2.9.7-21.el8_10.40:2.9.7-21.el8_10.4
Red Hat:enterprise_linux:8::appstreampython3-libxml2-debuginfobefore 0:2.9.7-21.el8_10.40:2.9.7-21.el8_10.4
Red Hat:enterprise_linux:8::baseoslibxml2before 0:2.9.7-21.el8_10.40:2.9.7-21.el8_10.4
Red Hat:enterprise_linux:8::baseospython3-libxml2before 0:2.9.7-21.el8_10.40:2.9.7-21.el8_10.4
Red Hat:enterprise_linux:9::appstreamlibxml2-debuginfobefore 0:2.9.13-14.el9_70:2.9.13-14.el9_7
Red Hat:enterprise_linux:9::appstreamlibxml2-debugsourcebefore 0:2.9.13-14.el9_70:2.9.13-14.el9_7
Red Hat:enterprise_linux:9::appstreamlibxml2-develbefore 0:2.9.13-14.el9_70:2.9.13-14.el9_7
Red Hat:enterprise_linux:9::appstreampython3-libxml2-debuginfobefore 0:2.9.13-14.el9_70:2.9.13-14.el9_7

+62

Same product

xmlsoft: all records

Other highest-scoring records for the same primary product.

  • CVE-2008-3529Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers to
    47Plan
  • CVE-2017-7376Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling
    46Plan
  • CVE-2022-40303An issue was discovered in libxml2 before 2.10.3.
    42Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-6021Jun 12, 2025 · Libxml2: integer overflow in xmlbuildqname() leads to stack buffer overflow in libxml2
    30Monitor
  • ← EarlierCVE-2025-8732Aug 8, 2025 · libxml2 xmlcatalog xmlParseSGMLCatalog recursion
    7Monitor
  • Later →CVE-2026-0989Jan 15, 2026 · Libxml2: unbounded relaxng include recursion leading to stack overflow
    14Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
libxml2 libxml22.10.0Vendor (CNA)
libxml2 libxml22.12.7+dfsg+really2.9.14-0.4ubuntu0.3Vendor (CNA)
libxml2 libxml22.9.1+dfsg1-3ubuntu4.13+esm9Vendor (CNA)
libxml2 libxml22.9.10+dfsg-5ubuntu0.20.04.10+esm2Vendor (CNA)
libxml2 libxml22.9.13+dfsg-1ubuntu0.9Vendor (CNA)
libxml2 libxml22.9.14+dfsg-1.3ubuntu3.5Vendor (CNA)
libxml2 libxml22.9.3+dfsg1-1ubuntu0.7+esm10Vendor (CNA)
libxml2 libxml22.9.4+dfsg1-6.1ubuntu1.9+esm5Vendor (CNA)
almalinux:libxml22.9.13-14.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:libxml2-devel2.9.13-14.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:python3-libxml22.9.13-14.el9_7 · AlmaLinux:9Package registry (OSV)
debian:libxml22.9.14+dfsg-1.3~deb12u5 · Debian:12Package registry (OSV)
opensuse:python-libxml2-python2.9.7-150000.3.88.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:libxml20:2.9.13-3.el9_2.10 · Red Hat:rhel_e4s:9.2::baseosPackage registry (OSV)
red hat:libxml2-160:2.15.2-0.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:libxml2-debuginfo0:2.9.13-3.el9_2.10 · Red Hat:rhel_e4s:9.2::appstreamPackage registry (OSV)
red hat:libxml2-debugsource0:2.9.13-3.el9_2.10 · Red Hat:rhel_e4s:9.2::appstreamPackage registry (OSV)
red hat:libxml2-devel0:2.9.13-3.el9_2.10 · Red Hat:rhel_e4s:9.2::appstreamPackage registry (OSV)
red hat:libxml2-python0:2.9.1-6.el7_9.14 · Red Hat:rhel_els:7Package registry (OSV)
red hat:libxml2-static0:2.9.1-6.el7_9.14 · Red Hat:rhel_els:7Package registry (OSV)
red hat:python3-libxml20:2.9.13-3.el9_2.10 · Red Hat:rhel_e4s:9.2::baseosPackage registry (OSV)
red hat:python3-libxml2-debuginfo0:2.9.13-3.el9_2.10 · Red Hat:rhel_e4s:9.2::appstreamPackage registry (OSV)
rocky linux:libxml20:2.9.13-14.el9_7 · Rocky Linux:9Package registry (OSV)
suse:libxml22.9.4-46.93.1 · SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5Package registry (OSV)
suse:libxml22.9.7-150000.3.88.1 · SUSE:Linux Enterprise Micro 5.2Package registry (OSV)
suse:libxml2-python2.9.14-150400.5.50.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:python-libxml22.9.4-46.93.1 · SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5Package registry (OSV)
suse:python-libxml2-python2.9.7-150000.3.88.1 · SUSE:Linux Enterprise Micro 5.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-0989127 days apartLibxml2: unbounded relaxng include recursion leading to stack overflow
    14Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-674 · Uncontrolled Recursion

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records