xorg-server / xwayland glamor font atlas Heap Buffer Overflow
Summary
| CVE | CVE-2026-55999 |
|---|---|
| State | PUBLISHED |
| Assigner | suse |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-08 09:16:29 UTC |
| Updated | 2026-07-09 16:39:17 UTC |
| Description | Local attackers with a X connection able to provide PCX fonts to the X server xorg-server before 21.2.24 and xwayland before 24.1.13 could cause a heap buffer overflow via SetFont due to missing glyph boundary checks. |
Risk And Classification
Primary CVSS: v3.1 8.5 HIGH from [email protected]
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS: 0.002840000 probability, percentile 0.202650000 (date 2026-07-08)
Problem Types: CWE-122 | CWE-122 CWE-122 Heap-based buffer overflow
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 8.5 | HIGH | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| 3.1 | CNA | CVSS | 8.5 | HIGH | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
LowUser Interaction
NoneScope
ChangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | X.Org | Xorg-server | affected 21.1.24 rpm | Not specified |
| CNA | X.Org | Xwayland | affected 24.1.13 rpm | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| www.openwall.com/lists/oss-security/2026/07/08/2 | [email protected] | www.openwall.com | |
| gitlab.freedesktop.org/xorg/xserver/-/commit/fbf7bac22e2c6bd627fb042742a23318263edae1 | [email protected] | gitlab.freedesktop.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Anonymous working with Trend Micro Zero Day Initiative. (en)
There are currently no legacy QID mappings associated with this CVE.