Skip to main content
Mallory
High

Stack-based buffer overflow in X.Org X server and Xwayland font alias resolution

IdentifiersCVE-2026-50256CWE-121· Stack-based Buffer Overflow

CVE-2026-50256 is a stack-based buffer overflow in the X.Org X server and Xwayland during font alias resolution. The flaw is caused by a length mismatch between the X server and libXfont2: the server allocates a 256-byte stack buffer for an alias target name, while libXfont2 permits alias target names up to 1024 bytes. When processing a font alias target name between 257 and 1023 bytes, the X server copies the name into the undersized stack buffer without sufficient bounds checking, resulting in a stack overflow. According to the provided advisory context, this affects X.Org X server versions prior to 21.1.23 and Xwayland versions prior to 24.1.12.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the X server, causing denial of service. If the X server is running with root privileges, the stack-based overflow may also enable privilege escalation.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by ensuring the X server does not run as root where feasible, and restrict the ability of untrusted clients or inputs to trigger font alias resolution paths. These are partial mitigations only; the primary remediation is to update to the fixed versions.

Remediation

Patch, then assume compromise.

Upgrade to fixed releases: xorg-server 21.1.23 or later and xwayland 24.1.12 or later, which include the vendor's fixes for this issue.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
X.OrgX Serverapplication
X.OrgXwaylandapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.