CVE-2025-11731: Libxslt: type confusion in exsltfuncresultcompfunction of libxslt
A flaw was found in the exsltFuncResultComp() function of libxslt, which handles EXSLT <func:result> elements during stylesheet parsing. Due to improper type handling, the function may treat an XML document node as a regular XML element node, resulting in a type confusion. This can cause unexpected memory reads and potential crashes. While difficult to exploit, the flaw could lead to application instability or denial of service.
Security readout for executives and security teams
Plain-English summary
This is a low-severity stability flaw in libxslt, a library used to process XSLT stylesheets. A specially formed stylesheet can trigger type confusion during parsing, potentially causing crashes. The cited scoring indicates high attack complexity and required user interaction, with availability impact only.
Executive priority
Treat as routine patch management unless the organization processes untrusted XSLT/XML in business-critical services. Prioritize affected internet-facing or multi-tenant parsing workflows, but this does not currently justify emergency response based on the supplied evidence.
Technical view
The flaw is in libxslt exsltFuncResultComp(), which handles EXSLT func:result elements during stylesheet parsing. Improper type handling may treat an XML document node as an XML element node, causing type confusion, unexpected memory reads, and potential crashes. CVSS 3.1 is 3.1: AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L.
Likely exposure
Exposure is most relevant where applications process untrusted or externally supplied XSLT/XML through libxslt. The bundle identifies affected Red Hat Enterprise Linux 7, 8, 9, 10, OpenShift Container Platform 4 RHCOS, and Red Hat Hardened Images; RHEL 6 status is unknown.
Exploitation context
The source bundle does not show KEV listing or active exploitation. Exploitation is described as difficult and would likely require a target to process attacker-influenced stylesheet content. Expected impact is application instability or denial of service, not confidentiality or integrity compromise.
Researcher notes
Focus assessment on stylesheet parsing paths and EXSLT func:result handling. The bundle supports denial-of-service concern through crashes and memory reads, but not code execution, data theft, public exploit availability, or active exploitation.
Mitigation direction
Check Red Hat advisory RHSA-2026:11015 for fixed package guidance.
Update affected libxslt packages through vendor-supported channels where fixes are available.
Restrict processing of untrusted XSLT stylesheets where business workflows permit.
Monitor vendor advisories for upstream libxslt and distribution-specific status changes.
Validation and detection
Inventory systems, containers, and images containing libxslt or libxslt-main.
Compare installed package versions against Red Hat CVE and errata status.
Identify applications that accept user-supplied XML or XSLT input.
Review crash logs for libxslt-related parser failures in exposed services.
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-843: 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-843 · source CWE mapping
Access of Resource Using Incompatible Type ('Type Confusion')
Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.