CVE-2025-11731

Deferred Deferred - Pending Action

BaseFortify

Publication date: 2025-10-14

Last updated on: 2026-06-30

Assigner: Red Hat, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-14

Last Modified

2026-06-30

Generated

2026-07-06

AI Q&A

2025-10-14

EPSS Evaluated

2026-07-05

NVD

CVE-2025-11731

Affected Vendors & Products

Vendor	Product	Version / Range
gnome	libxslt	*

Helpful Resources

Exploitability

CWE

KEV

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

Executive Summary

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]

Impact Analysis

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]

Detection Guidance

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]

Mitigation Strategies

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]

Hi! I’m here to help you understand CVE-2025-11731. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70