CVE-2025-7425

What it is

A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data tampering, service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2025-07-10 08:44 UTC ReservedThe CVE id was reserved by its CNA
2. 2025-07-10 14:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-11-06 01:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 7.8 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2025-07-10 14:15 UTC

Last modified

2026-11-06 01:17 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-416 · Use after free

Record status

Deferred

Attack profile CVSS 3.1 · 7.8

Attack vector

Local

Complexity

High

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

None

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-7425.md and follow it. Check whether this project is affected by CVE-2025-7425. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge