Local attackers with a X connection able to provide GLX commit to the X server xorg-server before 21.2.24 and xwayland before 24.1.13 could cause a Heap Use After Free, due to CommonMakeCurrent() pointing into potentially reallocated memory.
CVE-2026-56000
This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.0
- EG Score
- 9.0(medium)
- EPSS
- 11.7%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 8, 2026
Advisory Details (2)
Auto-updated Jul 8, 2026oss-security - FW: X.Org Security Advisory: multiple security issues X.Org X server and Xwayland
https://www.openwall.com/lists/oss-security/2026/07/08/2glx: free old context tag before allocating new one in CommonMakeCurrent (2779affb) · Commits · xorg / xserver · GitLab
https://gitlab.freedesktop.org/xorg/xserver/-/commit/2779affbdb4354e894f490e56f962527d6125043Vendor Advisories for CVE-2026-56000(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-08 19:23 UTCEG score recompute
- 2026-07-08 19:23 UTCGHSA enrichment
- 2026-07-08 15:41 UTCEG score recompute
- 2026-07-08 15:41 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 12:00 UTCEG score recompute
- 2026-07-08 12:00 UTCGHSA enrichment
- 2026-07-08 08:17 UTCEG score recompute
- 2026-07-08 08:16 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-416
- CVE-2010-3962NVD 8.1EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-0806NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-0249NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-4324NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-3328EG 8.8EPSS 98%HIGH
- CVE-2010-1772EG 8.8HIGH
- CVE-2010-1208EG 8.8EPSS 91%HIGH
- CVE-2010-0050EG 8.8EPSS 96%HIGH
- CVE-2010-0378EG 8.8EPSS 93%HIGH
- CVE-2009-3658EG 8.8EPSS 95%HIGH
Frequently asked(5)
What is CVE-2026-56000?
When was CVE-2026-56000 disclosed?
Is CVE-2026-56000 actively exploited?
What is the CVSS score of CVE-2026-56000?
How do I remediate CVE-2026-56000?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56000
Is Your Infrastructure Affected by CVE-2026-56000?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.