CVE-2025-11731
BaseFortify
Publication date: 2025-10-14
Last updated on: 2026-04-27
Assigner: Red Hat, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gnome | libxslt | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-843 | The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a type confusion flaw in the libxslt library's exsltFuncResultComp() function, which processes EXSLT <func:result> elements during XML stylesheet parsing. The function incorrectly treats an XML document node as a regular XML element node, causing it to misinterpret certain data fields. This leads to reading memory from unintended addresses, potentially causing application crashes or segmentation faults. [1]
How can this vulnerability impact me? :
The vulnerability can cause application instability or denial of service by crashing the application processing malicious XSL stylesheets. It is difficult to exploit and primarily results in denial-of-service conditions, potentially affecting any Linux system using libxslt. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for crashes or segmentation faults in applications using the libxslt library when processing XSL stylesheets, especially those containing EXSLT <func:result> elements. Since the flaw causes type confusion leading to memory reads and potential crashes, you can look for application logs indicating segmentation faults or abnormal termination related to libxslt usage. There are no specific commands provided to detect this vulnerability directly. However, you may use system logs (e.g., dmesg, journalctl) to identify crashes and use tools like 'strace' or 'gdb' to trace faults in applications processing XSL stylesheets. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding processing untrusted or malicious XSL stylesheets that use EXSLT <func:result> elements, as the vulnerability can be exploited remotely via such stylesheets. Additionally, updating the libxslt library to a patched version once available is recommended. Until a patch is applied, consider restricting or sandboxing applications that use libxslt to limit the impact of potential denial-of-service conditions caused by this vulnerability. [1]