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.

Published: 2025-10-14 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-11731 is rated Low Risk (18.5/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.26%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-11731

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.09% 0.26% +0.17%
2 2026-02-13 0.05% 0.09% +0.04%
3 2025-12-21 — 0.05% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-11731

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.1 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.6 1.4 [email protected]

Weakness enumeration for CVE-2025-11731

GitHub Security Advisory for CVE-2025-11731

GHSA-9f23-58rv-2hx4 · Severity: low — A flaw was found in the exsltFuncResultComp() function of libxslt, which handles EXSLT <func...

OS Trackers for CVE-2025-11731

vendor priority summary link
debian not yet assigned CVE-2025-11731 not yet assigned priority: Debian including 1 source packages (libxslt), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-11731
redhat low — https://access.redhat.com/security/cve/CVE-2025-11731
suse high CVE-2025-11731 severity important: SUSE including 276 source package names (0.6.18-12.38:libxslt1-1.1.34-150400.3.13.1, 1.1.0-1.1:libxslt1-1.1.34-150400.3.13.1, …), 675 product×package rows across 294 product lines (Container containers/open-webui, Container private-registry/harbor-nginx, … (294 product lines)): Fixed 440, Known Affected 231, First Fixed 4. https://www.suse.com/security/cve/CVE-2025-11731/
ubuntu low CVE-2025-11731 low priority: Ubuntu including 1 source packages (libxslt), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-11731

Affected software / configurations for CVE-2025-11731

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-11731

cvelogic Threat Intelligence