CVE-2025-10911: Libxslt: use-after-free with key data stored cross-rvt
A use-after-free vulnerability was found in libxslt while parsing xsl nodes that may lead to the dereference of expired pointers and application crash.
Security readout for executives and security teams
Plain-English summary
CVE-2025-10911 is a libxslt memory-safety flaw that can crash an application while parsing XSL nodes. Business impact is mainly service disruption, not data theft, based on current scoring. It requires user interaction and is not listed as known exploited in CISA KEV.
Executive priority
Treat as routine but timely patching. Elevate priority for systems where application availability is critical or where untrusted documents are transformed with libxslt. Current evidence supports moderate urgency, not emergency response.
Technical view
Red Hat describes a use-after-free in libxslt involving key data stored cross-rvt, leading to dereferencing expired pointers and application crash. CVSS 3.1 is 5.5: local attack vector, low complexity, no privileges, user interaction required, high availability impact, no confidentiality or integrity impact.
Likely exposure
Exposure is most relevant on affected Red Hat platforms and products carrying libxslt, including listed RHEL 6, 7, 8, 9, 10 variants, OpenShift Container Platform 4 rhcos, Red Hat Discovery 2, and Red Hat Hardened Images. Risk depends on whether local workflows or applications parse XSL content.
Exploitation context
The provided sources do not show active exploitation, and KEV is false. The documented impact is application crash from malformed parsing conditions. Because CVSS requires local access and user interaction, internet-wide urgency appears lower unless untrusted XSL processing is exposed through business applications.
Researcher notes
Evidence is limited to vendor CVE metadata, Red Hat advisories, Bugzilla, and upstream GNOME issue/MR references. The bundle does not provide exploit details, a public proof-of-concept status, or complete cross-distribution impact. Avoid assuming remote exploitability beyond the stated CVSS vector.
Mitigation direction
Apply the relevant Red Hat security errata for affected supported platforms.
Prioritize systems where libxslt processes user-supplied or partner-supplied XSL/XML content.
For non-Red Hat builds, check GNOME/libxslt and distribution vendor guidance.
Reduce processing of untrusted XSL where operationally feasible until patched.
Validation and detection
Inventory installed libxslt packages and container images across Linux estates.
Map assets to the affected Red Hat products and package names listed in the CVE data.
Confirm applicable RHSA updates are installed through standard patch compliance tooling.
Identify applications that parse XSL content and assess availability impact if they crash.
Monitor vendor advisories for corrected package details and backport status.
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-825: 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.
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.