CVE-2025-62229

7.3 HIGH 0.5% exploit odds No fix listed Memory safety Server

What it is

A flaw was found in the X.Org X server and Xwayland when processing X11 Present extension notifications. Improper error handling during notification creation can leave dangling pointers that lead to a use-after-free condition. This can cause memory corruption or a crash, potentially allowing an attacker to execute arbitrary code or cause a denial of service.

At a glance

Exploitability: Can be exploited locally on the machine with a low-privilege account. High risk of data tampering, service disruption.
Exploit odds: 0.5% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2025-10-30 06:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-11-05 17: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.5% in the next 30 days (EPSS).
Severity: 7.3 HIGH (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2025-10-30 06:15 UTC
Last modified: 2026-11-05 17:17 UTC
Exploit probability: 0.5% · EPSS, next 30 days
Weakness: CWE-416 · Use after free
Record status: Deferred

Attack profile CVSS 3.1 · 7.3

Attack vector: Local
Complexity: Low
Privileges needed: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
Availability: High

Raw vector

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

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-62229.md and follow it. Check whether this project is affected by CVE-2025-62229. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record