Quick answers
- Is CVE-2026-93516 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93516 being exploited in the wild.
- How severe is CVE-2026-93516?
- Medium severity, with a CVSS score of 5.5, 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-93516?
- 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-93516 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-93516?
- 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 vulnerability exists in passive grab management when XIRemoveMaster removes an XInput device. The vulnerability occurs because passive grabs store raw DeviceIntPtr pointers without lifetime management; when CloseDevice() frees the device struct, dangling pointers remain in grab->modifierDevice. Subsequent pointer events trigger CheckPassiveGrab(), which dereferences the invalid pointer in the XI code path, allowing authenticated X clients to crash the server or achieve code execution.
Affected products
- X.org X Server before 21.1.25
- X.org XWayland before 24.1.14
Timeline
- 2026-10-28: disclosed
- 2026-08-26: patched