Skip to content
Noroxi
CVE-2025-8732· NVD / CVE Program· CNA VulDB

libxml2 xmlcatalog xmlParseSGMLCatalog recursion

Noroxi assessment

Priority: Monitor (action score 7/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.21% (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: azl3 libxml2 2.11.5-8 on Azure Linux 3.0 2.11.5-9; azl3 libxml2 2.11.5-9 on Azure Linux 3.0 2.11.5-9; cbl2 libxml2 2.10.4-10 on CBL Mariner 2.0 2.10.4-11.
  • Severity is disputed: the assigning authority (CNA) scores it 4.8, NVD 1.9.

Low priority for now. Upgrade to azl3 libxml2 2.11.5-8 on Azure Linux 3.0 2.11.5-9; azl3 libxml2 2.11.5-9 on Azure Linux 3.0 2.11.5-9; cbl2 libxml2 2.10.4-10 on CBL Mariner 2.0 2.10.4-11 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

A vulnerability was found in libxml2 up to 2.14.5. It has been declared as problematic. This vulnerability affects the function xmlParseSGMLCatalog of the component xmlcatalog. The manipulation leads to uncontrolled recursion. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains, that "[t]he issue can only be triggered with untrusted SGML catalogs and it makes absolutely no sense to use untrusted catalogs. I also doubt that anyone is still using SGML catalogs at all."

LowCVSS 1.9 · v4.0—No exploit Fix available
Published
Aug 8, 2025
Updated
Jul 1, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

7

Monitor

Low priority for now.

CVSS
7 / 40 · 1.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · VulDB
4.8
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

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-8732

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
siemensruggedcom rst2428p firmware
siemensruggedcom rst2428p
ibmvios
ibmaix

Affected versions

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

  • ibm aix7.2.5 and later · before 7.2.5.12
  • ibm aix7.3.2 and later · before 7.3.3.3
  • ibm aix7.3.4
  • ibm vios4.1.0 and later · before 4.1.1.30
  • ibm vios4.1.2.0
  • siemens ruggedcom rst2428p firmwarebefore 4.0
  • xmlsoft libxml2before 2.15.2

Versions reported by the vendor

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

  • n/a libxml2

    • 2.14.0, 2.14.1, 2.14.2, 2.14.3, 2.14.4, 2.14.5affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12libxml2before 2.9.14+dfsg-1.3~deb12u62.9.14+dfsg-1.3~deb12u6
Debian:13libxml2before 2.12.7+dfsg+really2.9.14-2.1+deb13u32.12.7+dfsg+really2.9.14-2.1+deb13u3
Debian:14libxml2before 2.15.2+dfsg-0.12.15.2+dfsg-0.1
openSUSE:Leap 16.0libxml2before 2.13.8-160000.4.12.13.8-160000.4.1
openSUSE:Leap 16.0libxml2-pythonbefore 2.13.8-160000.4.12.13.8-160000.4.1
openSUSE:Leap 16.0libxsltbefore 1.1.43-160000.4.11.1.43-160000.4.1
openSUSE:Tumbleweedlibxml2before 2.14.5-4.12.14.5-4.1
SUSE:Linux Enterprise Micro 5.2libxml2before 2.9.7-150000.3.88.12.9.7-150000.3.88.1
SUSE:Linux Enterprise Micro 5.2libxml2before 2.9.7-150000.3.88.12.9.7-150000.3.88.1
SUSE:Linux Enterprise Micro 5.2python-libxml2-pythonbefore 2.9.7-150000.3.88.12.9.7-150000.3.88.1
SUSE:Linux Enterprise Micro 5.2python-libxml2-pythonbefore 2.9.7-150000.3.88.12.9.7-150000.3.88.1
SUSE:Linux Enterprise Micro 5.3libxml2before 2.9.14-150400.5.50.12.9.14-150400.5.50.1
SUSE:Linux Enterprise Micro 5.3libxml2-pythonbefore 2.9.14-150400.5.50.12.9.14-150400.5.50.1
SUSE:Linux Enterprise Micro 5.5libxml2before 2.10.3-150500.5.38.12.10.3-150500.5.38.1
SUSE:Linux Enterprise Micro 5.5libxml2before 2.10.3-150500.5.38.12.10.3-150500.5.38.1
SUSE:Linux Enterprise Micro 5.5libxml2-pythonbefore 2.10.3-150500.5.38.12.10.3-150500.5.38.1
SUSE:Linux Enterprise Micro 5.5libxml2-pythonbefore 2.10.3-150500.5.38.12.10.3-150500.5.38.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7libxml2before 2.12.10-150700.4.11.12.12.10-150700.4.11.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7libxml2-pythonbefore 2.12.10-150700.4.11.12.12.10-150700.4.11.1
SUSE:Linux Enterprise Server 16.0libxml2before 2.13.8-160000.4.12.13.8-160000.4.1
SUSE:Linux Enterprise Server 16.0libxml2-pythonbefore 2.13.8-160000.4.12.13.8-160000.4.1
SUSE:Linux Enterprise Server 16.0libxsltbefore 1.1.43-160000.4.11.1.43-160000.4.1
SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5libxml2before 2.9.4-46.93.12.9.4-46.93.1
SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5python-libxml2before 2.9.4-46.93.12.9.4-46.93.1

+6

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-32415Apr 17, 2025 · In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read.
    30Monitor
  • ← EarlierCVE-2025-6021Jun 12, 2025 · Libxml2: integer overflow in xmlbuildqname() leads to stack buffer overflow in libxml2
    30Monitor
  • Later →CVE-2025-9714Sep 10, 2025 · Stack overflow in libxml2
    22Monitor

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
azl3 libxml2 2.11.5-8 on Azure Linux 3.02.11.5-9 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 libxml2 2.11.5-9 on Azure Linux 3.02.11.5-9 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 libxml2 2.10.4-10 on CBL Mariner 2.02.10.4-11 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 libxml2 2.10.4-11 on CBL Mariner 2.02.10.4-11 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:libxml22.9.14+dfsg-1.3~deb12u6 · Debian:12Package registry (OSV)
opensuse:libxml22.10.3-150500.5.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:libxml2-python2.10.3-150500.5.38.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:libxslt1.1.43-160000.4.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:python-libxml2-python2.9.7-150000.3.88.1 · openSUSE:Leap 15.6Package 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.10.3-150500.5.38.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:libxml2-python2.9.14-150400.5.50.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:libxslt1.1.43-160000.4.1 · SUSE:Linux Enterprise Server 16.0Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

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

No commit or PR link among the references.

Credits

All researchers

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

No credits in the CNA record.

Variant candidates

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

No nightly-computed relations.

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

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

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
Integrity
Availability
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-404 · Improper Resource Shutdown or Release

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

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

Change log

  1. Fix✗ → ✓

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

References

Show all references (4 more)

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

All records