Quick answers
- Is CVE-2026-88812 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88812 being exploited in the wild.
- How severe is CVE-2026-88812?
- High severity, with a CVSS score of 7.8, published 27 October 2026.
- Which products and versions are affected?
- X.Org Foundation X Server before 21.1.25; X.Org Foundation X Wayland before 24.1.14.
- Is there a fix for CVE-2026-88812?
- Yes: fixed in X Server 21.1.25, X Wayland 24.1.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88812 attacked?
- It is attacked over the network or with local access, in a hosted service.
- Am I affected by CVE-2026-88812?
- Check whether you run X.Org Foundation X Server or X.Org Foundation X Wayland at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: X Server 21.1.25, X Wayland 24.1.14
Technical details
A double-free vulnerability exists in _CheckSetDoodad() within X.Org X Server's XKB geometry handling. When font string allocation fails during doodad text processing, the error handler frees the text pointer without NULLing it; since the doodad was already added to the geometry, subsequent cleanup via _XkbClearDoodad() frees the same dangling pointer again. Local or network-attached X clients can trigger this via malformed XKB SetGeometry requests.
Affected products
- X.Org Foundation X Server before 21.1.25
- X.Org Foundation X Wayland before 24.1.14
Timeline
- 2026-10-27: disclosed
- 2026-08-26: other: Fix committed