CVE-2025-7425: Libxslt: libxml2: heap use-after-free in libxslt caused by atype corruption in xmlattrptr
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-7425 is a memory-safety flaw in libxslt-related XSLT processing. Specially crafted processing conditions can make software reuse freed memory, potentially causing crashes or corrupting data and execution state. Red Hat identifies multiple supported RHEL streams and OpenShift 4.12 as affected.
Executive priority
Treat as a high-priority patch-management issue, especially on shared processing systems or services handling untrusted XML/XSLT. It is not presented as an emergency internet-wide threat: exploitation is rated local and difficult, and active exploitation is unsupported. Remediate promptly through Red Hat guidance and validate application-level reachability.
Technical view
Corruption of attribute-type flags during XSLT operations, including key() processing that creates tree fragments, can prevent correct cleanup of ID attributes. Subsequent access to freed heap memory produces a CWE-416 use-after-free. CVSS 3.1 rates it 7.8, with local access, high complexity, no privileges or interaction, changed scope, and high integrity and availability impact.
Likely exposure
Exposure is most likely where listed Red Hat systems contain the affected libxml2 or libxslt packages and applications perform XSLT transformations. The bundle names RHEL 7 ELS, numerous RHEL 8 and 9 streams, RHEL 10, and OpenShift 4.12. Installed-package presence alone does not prove the vulnerable processing path is reachable.
Exploitation context
The supplied CVSS describes local, high-complexity exploitation without privileges or user interaction. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or public weaponization. KEV absence does not prove exploitation has never occurred.
Researcher notes
The bundle has attribution ambiguity: the title references both libxslt and libxml2, while affected entries include both packages and GNOME libxml2 is marked unaffected. Exact fixed-version boundaries are not supplied here. Researchers should preserve package, linkage, transformation-path, and crash evidence, and consult each referenced advisory before concluding exposure or remediation status.
Mitigation direction
Inventory libxml2 and libxslt packages across listed RHEL and OpenShift releases.
Review the applicable Red Hat advisory for corrected package availability and installation guidance.
Prioritize systems where applications process untrusted or attacker-influenced XML and XSLT content.
Reduce untrusted XSLT processing where operationally feasible until vendor remediation is applied.
Restart or redeploy dependent services if required by the applicable vendor advisory.
Validation and detection
Compare installed package builds with the exact affected builds and applicable Red Hat errata.
Identify applications and containers dynamically or statically using libxslt or libxml2.
Confirm whether those applications execute XSLT transformations on attacker-influenced inputs.
After remediation, verify package provenance, deployed versions, and required service restarts.
Monitor exposed processors for abnormal crashes or memory-corruption symptoms; these are not proof of exploitation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
3ADP providers
38Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.