CVE-2026-50258: Xorg-x11-server: xorg-x11-server-xwayland: xorg-x11-server: stack buffer overflow in xkb key types due to unchecked shift levels
A stack-based buffer overflow flaw was found in the X.Org X server and Xwayland. The X server has multiple stack buffers sized XkbMaxShiftLevel * XkbNumKbdGroups but CheckKeyTypes() does not verify or clamp non-canonical key types to XkbMaxShiftLevel. A client can change key types to excessive shift levels and trigger stack overflows. This is caused by an incomplete fix of CVE-2025-26597. This may be used to crash the server, or for privilege escalation if the X server runs as root.
Security readout for executives and security teams
Plain-English summary
CVE-2026-50258 is a local memory corruption flaw in X.Org X server and Xwayland. A logged-in client may crash the display server and, where the X server runs as root, potentially escalate privileges. This is high urgency for Linux workstation, remote desktop, and server environments that include the listed Red Hat Xorg, Xwayland, or TigerVNC packages.
Executive priority
Schedule expedited patching for affected Linux desktop, VDI, and remote GUI systems. This is not internet-remote based on the provided CVSS vector, but it can turn ordinary local access into full system compromise in root-running X server scenarios.
Technical view
CheckKeyTypes() fails to clamp non-canonical XKB key types to XkbMaxShiftLevel. Excessive shift levels can overflow stack buffers sized by XkbMaxShiftLevel * XkbNumKbdGroups. The issue is CWE-121, CVSS 7.8, local attack vector, low complexity, low privileges, no user interaction. Sources identify it as an incomplete fix for CVE-2025-26597.
Likely exposure
Exposure is most likely on affected Red Hat Enterprise Linux 7 ELS, 8, 9, 10, and listed lifecycle variants running xorg-x11-server, xorg-x11-server-Xwayland, or tigervnc packages. Systems with local graphical sessions, Xwayland, or VNC-style desktop access deserve priority review.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires local client access, but impact can include server crash or privilege escalation if the X server runs as root. Treat untrusted local users, shared desktops, and remote GUI environments as higher-risk contexts.
Researcher notes
Focus validation on XKB key type handling and package lineage, especially the incomplete CVE-2025-26597 fix. The bundle names Red Hat affected builds but does not provide exploit proof, fixed version details, or cross-distribution status. Avoid extrapolating beyond the listed products.
Mitigation direction
Apply the relevant Red Hat RHSA update for each affected release and package.
Prioritize systems running Xorg, Xwayland, or TigerVNC with multiple local users.
Check vendor guidance for lifecycle-specific fixes before assuming package parity.
Reduce unnecessary graphical or VNC services until updates are applied.
Avoid relying on unlisted workarounds as complete remediation.
Validation and detection
Inventory RHEL release, lifecycle channel, and installed Xorg, Xwayland, and TigerVNC packages.
Compare installed package versions against the affected package list in the source bundle.
Confirm the applicable Red Hat erratum has been applied for each host.
Identify whether Xorg or Xwayland runs with elevated privileges on affected systems.
Review remote desktop hosts separately; TigerVNC is listed as affected for RHEL 8 and 9.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
2ADP providers
27Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.