Quick answers
- Is CVE-2026-93536 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93536 being exploited in the wild.
- How severe is CVE-2026-93536?
- Medium severity, with a CVSS score of 5.3, published 28 October 2026.
- Which products and versions are affected?
- X.Org X Server before 21.1.25; X.Org XWayland before 24.1.14.
- Is there a fix for CVE-2026-93536?
- Yes: fixed in X Server 21.1.25, XWayland 24.1.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93536 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-93536?
- Check whether you run X.Org X Server or X.Org XWayland 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, XWayland 24.1.14
Technical details
A use-after-free in GestureBuildSprite() occurs when gesture sprite traces containing unrefcounted window pointers are not cleaned up during window destruction, leaving dangling pointers. If a device supports gestures but lacks a TouchClass, the cleanup logic skips gesture sprite cleanup, and DeliverOneGestureEvent() later dereferences the stale pointer via DeepestSpriteWin(&gi->sprite)->drawable.id. The vulnerability requires an authenticated X client to trigger window destruction during an active gesture.
Affected products
- X.Org X Server before 21.1.25
- X.Org XWayland before 24.1.14
Timeline
- 2026-10-28: disclosed: CVE-2026-93536 published
- 2026-09-03: patched: Fix committed (efcfd8ac) by Peter Hutterer