Quick answers
- Is CVE-2026-93522 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93522 being exploited in the wild.
- How severe is CVE-2026-93522?
- High severity, with a CVSS score of 7.8, published 28 October 2026.
- Which products and versions are affected?
- X.Org X Server before 21.1.15; X.Org XWayland before 24.1.14.
- Is there a fix for CVE-2026-93522?
- Yes: fixed in X Server 21.1.15, XWayland 24.1.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93522 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-93522?
- 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.15, XWayland 24.1.14
Technical details
A heap buffer overflow exists in the glamor_upload_boxes() function due to mismatched size calculations: the tmp_bits buffer is allocated based on destination pixmap height but indexed using source coordinates, causing out-of-bounds writes when the source is taller than the destination. An authenticated X client can trigger this via the CopyArea path by supplying crafted parameters to cause a heap overflow. The fix adjusts buffer sizing to account for source coordinate mapping relative to the destination.
Affected products
- X.Org X Server before 21.1.15
- X.Org XWayland before 24.1.14
Timeline
- 2026-10-28: disclosed: CVE-2026-93522 published