CVE-2025-7425

Libxslt: libxml2: heap use-after-free in libxslt caused by atype corruption in xmlattrptr

HIGH
7.8
CVSS Score
Published: July 10, 2025 at 01:53 PM UTC
Updated: October 15, 2026 at 02:18 AM UTC
19 products affected across 3 vendorsEnterprise LinuxLIBXML2OpenShift Container Platform

Using Red Hat Enterprise Linux 7 Extended Lifecycle Support by Red Hat?

Get instant alerts when new vulnerabilities affect Red Hat Enterprise Linux 7 Extended Lifecycle Support - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.4%
SSVC
PoC

Description

A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0
Affected range stops below 2.15.2, so it looks safe — our inference, not a vendor statement
All versions
Vendor states this is fixed in 0:1.1.39-8.el10_0 (unaffected)
Vendor states this is fixed in 0:2.12.5-8.el10_0 (unaffected)
Vendor states this is fixed in 0:2.9.1-6.el7_9.12 (unaffected)
Vendor states this is fixed in 0:2.9.13-1.el9_0.6 (unaffected)
Vendor states this is fixed in 0:2.9.13-11.el9_4 (unaffected)
Vendor states this is fixed in 0:2.9.13-11.el9_6 (unaffected)
Vendor states this is fixed in 0:2.9.13-3.el9_2.8 (unaffected)
Vendor states this is fixed in 0:2.9.7-13.el8_6.11 (unaffected)
Vendor states this is fixed in 0:2.9.7-16.el8_8.10 (unaffected)
Vendor states this is fixed in 0:2.9.7-21.el8_10.2 (unaffected)
Vendor states this is fixed in 0:2.9.7-9.el8_2.4 (unaffected)
Vendor states this is fixed in 0:2.9.7-9.el8_4.7 (unaffected)
Vendor states this is fixed in 6 (unknown)
Vendor states this is fixed in 4.19.9.6.202508271124-0 (unaffected)
Vendor states this is fixed in 412.86.202509030110-0 (unaffected)
Vendor states this is fixed in 413.92.202509030117-0 (unaffected)
Vendor states this is fixed in 414.92.202508270040-0 (unaffected)
Vendor states this is fixed in 415.92.202508192014-0 (unaffected)
Vendor states this is fixed in 416.94.202508261955-0 (unaffected)
Vendor states this is fixed in 417.94.202508141510-0 (unaffected)
Vendor states this is fixed in 418.94.202508261658-0 (unaffected)
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement

References (43)

SSVC — Action Prioritization

SSVCPoCNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHredhat
Attack Vector
LOCAL
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card