CVE-2025-8732Public exploit

Local process crash via self-referencing SGML catalog

Published Aug 8, 2025 · Updated Jun 2, 2026

Uncontrolled recursion in libxml2 2.14.0 through 2.14.5 allows local users to crash a consuming process with a crafted SGML catalog. xmlParseSGMLCatalog follows multiple CATALOG directives that point back to the same file, recursively reentering xmlExpandCatalog without deduplicating the expanded filename until the call stack overflows. Triggering requires an untrusted local SGML catalog; Siemens also identifies RUGGEDCOM RST2428P before V4.0 as affected, while the libxml2 maintainer disputes the practical security relevance.

CVSS severity4.8
Medium
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Uncontrolled recursion in libxml2 2.14.0 through 2.14.5 allows local users to crash a consuming process with a crafted SGML catalog. xmlParseSGMLCatalog follows multiple CATALOG directives that point back to the same file, recursively reentering xmlExpandCatalog without deduplicating the expanded filename until the call stack overflows. Triggering requires an untrusted local SGML catalog; Siemens also identifies RUGGEDCOM RST2428P before V4.0 as affected, while the libxml2 maintainer disputes the practical security relevance.

The record

CVE
CVE-2025-8732
Published
Aug 8, 2025
Updated
Jun 2, 2026
Vendor
XMLSoft
Product
libxml2
Classifications
CWE-404, CWE-674, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 8, 2025CVE publishedPublication date reported by the CVE source.
  2. Jun 2, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.14.0
  2. Affected versionversion=2.14.1
  3. Affected versionversion=2.14.2
  4. Affected versionversion=2.14.3
  5. Affected versionversion=2.14.4
  6. Affected versionversion=2.14.5

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

XMLSoft · libxml2version=2.14.0; version=2.14.1; version=2.14.2; version=2.14.3; version=2.14.4; version=2.14.5
Siemens · RUGGEDCOM RST2428Pversion=0 <V4.0

Published CVSS scores

1.7VulDB CNAAV:L/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:ND/RC:C
4.8Siemens ProductCERTCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
4.8VulDB CNACVSS: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
3.3VulDB CNACVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:X/RC:C
3.3Siemens ProductCERTCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
3.3VulDB CNACVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:X/RC:C

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-404Improper Resource Shutdown or Release
CWE-674Uncontrolled Recursion
T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo