CVE-2026-50256: Xorg-x11-server: xorg-x11-server-xwayland: xorg-x11-server: stack buffer overflow in font alias resolution due to libxfont2 name length mismatch
A stack-based buffer overflow flaw was found in the X.Org X server and Xwayland. A mismatch between the X server and the libXfont2 library's maximum font name length can cause a stack buffer overflow during font alias resolution. The server allocates a 256 byte stack buffer but libXfont2's alias target name length is 1024 bytes. A font alias name between 257 and 1023 bytes causes the X server to copy that name into the undersized stack buffer without further checks. 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
A flaw in the X.Org X server and Xwayland lets a local user crash the graphical display service or potentially take it over. It happens when the server processes an unusually long font alias name and writes it into a memory area that is too small. On systems where the X server runs with high privileges, this could allow the attacker to gain root-level control of the machine.
Executive priority
Treat as a near-term patching priority for Linux desktops, VDI, and remote-graphics servers. It is not remotely exploitable and is not on CISA KEV, but the local privilege-escalation path on root-privileged X servers makes it a meaningful risk on shared or multi-user Linux systems. Fold into the next standard patch cycle and expedite for exposed multi-user hosts.
Technical view
A size mismatch between the X server and libXfont2 creates a stack-based buffer overflow (CWE-121) during font alias resolution. The X server allocates a 256-byte stack buffer while libXfont2 permits alias target names up to 1024 bytes. An alias name between 257 and 1023 bytes is copied into the smaller buffer without bounds checking. CVSS 3.1 is 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting local, low-complexity, low-privilege exploitation with full impact.
Likely exposure
Red Hat lists RHEL 7 ELS, 8 (including AUS/EUS/E4S/TUS variants), 9, and 10 as affected via xorg-x11-server, xorg-x11-server-Xwayland, and tigervnc packages. Any workstation, thin client, VDI host, or remote-desktop server running X.Org or Xwayland is potentially exposed, especially multi-user systems where local accounts exist.
Exploitation context
Attack vector is local and requires authenticated low-privilege access; no user interaction is needed. Not listed in CISA KEV and no public exploitation has been cited in the source bundle. Impact escalates to privilege escalation when the X server runs as root, which is common on traditional X11 desktop and VNC deployments.
Researcher notes
Root cause is a constant mismatch: X server uses a 256-byte on-stack buffer for font alias resolution while libXfont2 exposes names up to 1024 bytes. Trigger surface is font alias handling, so review any path that lets a local user influence font configuration or font paths. Multiple RHSA errata cover RHEL 7 ELS through 10 including AUS/EUS/E4S/TUS streams; verify the correct advisory for your specific channel. No KEV listing and no public PoC cited in bundle.
Mitigation direction
Apply the Red Hat RHSA errata for xorg-x11-server, xorg-x11-server-Xwayland, and tigervnc matching your RHEL release channel.
Prioritize patching multi-user systems, jump hosts, VDI, and VNC/RDP gateways where local accounts exist.
Restrict local shell access on graphical hosts until packages are updated.
Where feasible, prefer rootless Xwayland or Wayland sessions over root-privileged X servers.
Monitor vendor guidance for downstream distributions not yet patched and track RHSA advisories for additional streams.
Validation and detection
Inventory hosts with xorg-x11-server, xorg-x11-server-Xwayland, libXfont2, or tigervnc installed.
Compare installed package versions against the fixed NEVRAs listed in the linked RHSA advisories for your RHEL stream.
Confirm no residual older X server binaries remain after update and restart affected sessions.
Review whether the X server on each host runs as root and record hosts where privilege escalation risk is highest.
Check auditd or journal logs for unexpected X server crashes that could indicate probing.
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.
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
ADP timelineredhat-SADP
Reported to Red Hat.
Source timelineredhat
Reported to Red Hat.
May 15, 2026, 03:14 UTC (UTC+00:00)
ADP timelineredhat-SADP
Made public.
Jun 2, 2026, 00:00 UTC (UTC+00:00)
Source timelineredhat
Made public.
Jun 2, 2026, 00:00 UTC (UTC+00:00)
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
Jun 4, 2026, 14:55 UTC (UTC+00:00)
CVE publishedCVE Program
The CVE record was published.
Jun 5, 2026, 10:31 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Jul 13, 2026, 12:05 UTC (UTC+00:00)
ADP provider summaries
CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPxorg-x11-server: xorg-x11-server-Xwayland: xorg-x11-server: stack buffer overflow in font alias resolution due to libXfont2 name length mismatch
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.