CVE-2025-32414VulnerabilityPublished 12 Aug 2025Updated 21 Oct 2026

Red Hat Security Advisory: libxml2 security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-32415

Authoritative record:CVE-2025-32414· Medium 5.6

Not known to be exploited · CVSS 5.6 Medium : upgrade the Debian debian/libxml2 package to 2.14.2 or 2.13.8 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS base score

5.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.14.2, 2.13.8

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade the Debian debian/libxml2 package to 2.14.2 or 2.13.8.

Affected software

Product	Affected	Fixed in
Debiandebian/libxml2`pkg:deb/debian/libxml2`Other threats	Affected <2.13.8 >=2.14.0 <2.14.2 =0 =2.14.0	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

Red Hat has released updated libxml2 packages for Red Hat Enterprise Linux 9.2 to address these vulnerabilities. Users should apply the official security update as described in Red Hat advisory RHSA-2025:13683. For detailed update instructions, refer to https://access.redhat.com/articles/11258. No additional mitigation steps are indicated by the vendor.

Description

The libxml2 library is a development toolbox providing the implementation of various XML standards. Security Fix(es): * libxml2: Out-of-Bounds Read in libxml2 (CVE-2025-32414) * libxml2: Out-of-bounds Read in xmlSchemaIDCFillNodeTables (CVE-2025-32415) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerabilities allow out-of-bounds reads which may lead to information disclosure or application instability when processing specially crafted XML data. Red Hat rates the security impact as moderate. There are no known exploits in the wild at this time.

Summary

The libxml2 library, which implements various XML standards, contains two security flaws involving out-of-bounds reads: CVE-2025-32414 and CVE-2025-32415. These vulnerabilities relate to improper memory access in libxml2 and specifically in the xmlSchemaIDCFillNodeTables function. Red Hat has released updated libxml2 packages for Red Hat Enterprise Linux 9.2 to fix these issues. No CVSS score is provided in the advisory, but the impact is considered moderate.

CWE-393Return of Wrong Status Code (opens in a new tab)
Base weakness
A function or operation returns an incorrect return value or status code that does not indicate the true result of execution, causing the product to modify its behavior based on the incorrect result.
CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Aug 2026, 16:54 UTC

WeaknessesCWE-393, CWE-125

Technical details

References

Community reviews

Related threats