Quick answers
- Is CVE-2026-93521 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93521 being exploited in the wild.
- How severe is CVE-2026-93521?
- High severity, with a CVSS score of 7.8, published 28 October 2026.
- Which products and versions are affected?
- X.Org X Server before 2.1.25; X.Org XWayland before 24.4.14.
- Is there a fix for CVE-2026-93521?
- Yes: fixed in X Server 2.1.25, XWayland 24.4.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93521 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-93521?
- 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 2.1.25, XWayland 24.4.14
Technical details
The vulnerability exists in RRChangeProviderProperty() in the RandR extension, where incorrect size and offset calculations in PropModePrepend (and affecting PropModeAppend) cases cause a buffer overflow. Authenticated X clients can trigger this by crafting malicious RandR property modification requests. Fixes are available in X.Org X Server 2.1.25 and XWayland 24.4.14.
Affected products
- X.Org X Server before 2.1.25
- X.Org XWayland before 24.4.14
Timeline
- 2026-10-28: disclosed