Skip to main content
CVE-2025-32415VulnerabilityPublished Updated

CVE-2025-32415: xmlsoft libxml2 · Improper Validation of Specified Quantity in Input

Affects xmlsoft libxml2Source CVE Database V5

0

Not known to be exploited · CVSS 2.9 Low : upgrade to 2.14.2 or 2.13.8 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
2.9Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.14.2, 2.13.8
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade debian/libxml2 to 2.14.2 or 2.13.8.

Affected software

ProductAffectedFixed in
Debiandebian/libxml2pkg:deb/debian/libxml2Other threatsAffected
  • <2.13.8
  • <2.14.2
Fixed in
  • 2.13.8
  • 2.14.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-32415, organizations should promptly update libxml2 to version 2.13.8 or 2.14.2 and later, where the vulnerability is patched. Conduct an inventory of all software components and applications that utilize libxml2 for XML processing to ensure they are not running vulnerable versions. Implement strict input validation and sanitization for all XML documents and schemas, especially those received from untrusted or external sources. Where possible, restrict the processing of XML schemas with complex identity constraints or disable schema validation if not required. Employ application-level sandboxing or containerization to limit the impact of potential crashes caused by malformed XML inputs. Monitor logs and application behavior for anomalies related to XML processing failures. Finally, coordinate with software vendors and developers to ensure timely patching and secure coding practices around XML handling.

Description

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. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.

References

Community reviews

Loading reviews…