# CVE-2025-11731: Libxslt: type confusion in exsltfuncresultcompfunction of libxslt

> A type confusion flaw in libxslt allows attackers to cause application crashes and denial of service via crafted XML stylesheets.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Oct 2025
- **Updated:** 1 Sep 2026
- **Also known as:** AZL-70550, AZL-70601, BELL-CVE-2025-11731, DEBIAN-CVE-2025-11731, ECHO-c04a-8ebf-d378, GHSA-9f23-58rv-2hx4, OESA-2026-1724, OESA-2026-1725, OESA-2026-1726, OESA-2026-1727, OESA-2026-1728, SUSE-SU-2025:3743-1, SUSE-SU-2025:3778-1, UBUNTU-CVE-2025-11731, openSUSE-SU-2025:15641-1

## What is CVE-2025-11731?

CVE-2025-11731 is a low-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2025-11731?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libxslt` | SUSE:Enterprise Storage 7.1 | All versions | 1.1.32-150000.3.28.1 |
| `libxslt` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.1.32-150000.3.28.1 |
| `libxslt` | SUSE:Linux Enterprise Micro 5.1 | All versions | 1.1.32-150000.3.28.1 |
| `libxslt` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.1.32-150000.3.28.1 |
| `libxslt` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 1.1.28-17.21.1 |
| `libxslt` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 1.1.32-150000.3.28.1 |
| `libxslt` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 1.1.28-17.21.1 |
| `libxslt` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 1.1.32-150000.3.28.1 |
| `libxslt-python` | openSUSE:Leap 15.6 | All versions | 1.1.32-150000.3.28.1 |
| `libxslt` | openSUSE:Tumbleweed | All versions | 1.1.43-4.1 |

## How do I fix CVE-2025-11731?

Apply the vendor's patch.

## Is CVE-2025-11731 being exploited?

There is no known exploitation of CVE-2025-11731 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11731 and fix it if it is affected.

What it is: CVE-2025-11731 is a low-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-11731 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11731/ (Markdown: https://insights.sbomify.com/CVE-2025-11731/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11731
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11731
- OSV: https://osv.dev/vulnerability/CVE-2025-11731

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11731/
Summaries are generated and may contain mistakes; the official description above is the record.