CVE-2025-7424VulnerabilityPublished 10 Jul 2025Updated 12 Oct 2026

CVE-2025-7424: GNOME libxslt · Type Confusion

Affects GNOME libxsltSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.1.44 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.1.44

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade GNOME libxslt to 1.1.44.

Affected software

Product	Affected	Fixed in
GNOMElibxslt	Affected <1.1.44	Fixed in 1.1.44
Red HatRed Hat Enterprise Linux 10	Affected–	Fixed in–
Red HatRed Hat Hardened Images	Affected–	Fixed in–
Red HatRed Hat Enterprise Linux 6	Affected–	Fixed in–
Red HatRed Hat Enterprise Linux 7	Affected–	Fixed in–
Red HatRed Hat Enterprise Linux 8	Affected–	Fixed in–
Red HatRed Hat Enterprise Linux 9	Affected–	Fixed in–
Red HatRed Hat OpenShift Container Platform 4	Affected–	Fixed in–

AI-suggested

Official patches are available from Red Hat for affected libxslt packages in Red Hat Enterprise Linux 10 and related distributions. Users should apply the updates provided in advisories RHBA-2025:12345 and RHSA-2026:11015 to remediate this vulnerability. Patch details and update instructions are available at Red Hat's customer portal. No additional mitigations are indicated by the vendor.

Description

A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion during XML transformations. This vulnerability allows an attacker to crash the application or corrupt memory. In some cases, it may lead to denial of service or unexpected behavior.

Impact

Exploitation of this vulnerability can cause application crashes or memory corruption, leading to denial of service or unexpected behavior in applications using libxslt for XML transformations. There is no indication of confidentiality or integrity impact. No known exploits in the wild have been reported at this time.

Summary

The vulnerability in libxslt arises from type confusion involving the xmlNode.psvi field, which is used interchangeably for stylesheet and source nodes. This can cause heap use-after-free or memory corruption during XML processing. The issue is tracked under CVE-2025-7424 and has been assigned a CVSS 3.1 score of 7.5 (high severity) with network attack vector, low attack complexity, no privileges required, and no user interaction needed. Red Hat's advisories (RHBA-2025:12345 and RHSA-2026:11015) confirm the existence of this flaw and provide updated libxslt packages that fix the problem.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Jul 2026, 22:22 UTC

Technical details

References

Community reviews

Related threats