Application crash via document-node type confusion
Published Oct 14, 2025 · Updated Oct 14, 2025
Type confusion in libxslt on affected Red Hat platforms allows remote attackers to crash applications via a crafted XSL stylesheet. exsltFuncResultComp() walks past the expected func:function ancestor and treats an XML document node's ns pointer as element fields, causing an invalid memory read. Exploitation requires the stylesheet to be processed, and Red Hat reports a process crash only, with no data corruption or code execution.
Summary
What happened
Type confusion in libxslt on affected Red Hat platforms allows remote attackers to crash applications via a crafted XSL stylesheet. exsltFuncResultComp() walks past the expected func:function ancestor and treats an XML document node's ns pointer as element fields, causing an invalid memory read. Exploitation requires the stylesheet to be processed, and Red Hat reports a process crash only, with no data corruption or code execution.
The record
- CVE
- CVE-2025-11731
- Published
- Oct 14, 2025
- Updated
- Oct 14, 2025
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-843, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo