CVE-2026-56000

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-08. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-42202 (ENISA EUVD) · GHSA-4gcc-rqqq-58jp (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available.
Web page

oss-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/2
Web page

glx: free old context tag before allocating new one in CommonMakeCurrent (2779affb) · Commits · xorg / xserver · GitLab

https://gitlab.freedesktop.org/xorg/xserver/-/commit/2779affbdb4354e894f490e56f962527d6125043

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatxorg-x11-server-Xwayland-0:22.1.9-8.el9_4.32026-08-10redhat
redhatxorg-x11-server-Xwayland-0:23.2.7-6.el9_6.32026-08-05redhat
redhatxorg-x11-server-Xwayland-0:24.1.5-6.el10_0.22026-08-04redhat
redhatxorg-x11-server-Xwayland-0:24.1.9-4.el9_8.32026-07-13redhat
redhatxorg-x11-server-Xwayland-0:24.1.9-4.el10_2.32026-07-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 5 ecosystems)
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
xorg-server—
  • every version up to 21.1.24-r0: fixed in 21.1.24-r0
—
xwayland—
  • every version up to 24.1.13-r0: fixed in 24.1.13-r0
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
xorg-server2:21.1.10-1 ... 2:21.1.9-1+hurd.1 (42 versions)
  • every version on: no fix on record
—
xwayland2:22.1.9-1 ... 2:24.1.9-1 (24 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
xorg-server2:21.1.16-1.3, 2:21.1.16-1.3+deb13u1, 2:21.1.16-1.3+deb13u2, 2:21.1.16-1.3+deb13u3
  • every version up to 2:21.1.16-1.3+deb13u4: fixed in 2:21.1.16-1.3+deb13u4
—
xwayland2:24.1.10-1 ... 2:24.1.9-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
xorg-server2:21.1.16-1.3 ... 2:21.1.23-1 (7 versions)
  • every version up to 2:21.1.24-1: fixed in 2:21.1.24-1
—
xwayland2:24.1.10-1 ... 2:24.1.9-1 (6 versions)
  • every version up to 2:24.1.13-1: fixed in 2:24.1.13-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
xorg-server2:1.20.11-1 ... 2:21.1.9-1+hurd.1 (61 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 362 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 262 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-11-08 05:49 UTCEchelonGraph re-scored
  8. 2026-11-08 05:49 UTCVendor advisory
  9. 2026-11-08 05:49 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  10. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-10-31 20:54 UTCEchelonGraph re-scored
  18. 2026-10-31 20:54 UTCVendor advisory
  19. 2026-10-31 20:54 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  20. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  23. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
Show 75 more
  1. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-25 14:18 UTCEchelonGraph re-scored
  3. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-24 12:02 UTCEchelonGraph re-scored
  5. 2026-10-24 12:02 UTCVendor advisory
  6. 2026-10-24 12:02 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  7. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-18 03:29 UTCEchelonGraph re-scored
  14. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-17 03:10 UTCEchelonGraph re-scored
  16. 2026-10-17 03:10 UTCVendor advisory
  17. 2026-10-17 03:10 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  18. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-10-12 15:55 UTCEchelonGraph re-scored
  24. 2026-10-11 19:38 UTCEchelonGraph re-scored
  25. 2026-10-11 16:53 UTCEchelonGraph re-scored
  26. 2026-10-11 14:16 UTCEchelonGraph re-scored
  27. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  31. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  35. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-10-01 16:21 UTCEchelonGraph re-scored
  39. 2026-10-01 16:21 UTCVendor advisory
  40. 2026-10-01 16:21 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  41. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  43. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  44. 2026-09-28 13:32 UTCEchelonGraph re-scored
  45. 2026-09-28 13:32 UTCVendor advisory
  46. 2026-09-28 13:32 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  47. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  50. 2026-09-24 11:54 UTCEchelonGraph re-scored
  51. 2026-09-24 11:54 UTCVendor advisory
  52. 2026-09-24 11:54 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  53. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  54. 2026-09-23 06:14 UTCEchelonGraph re-scored
  55. 2026-09-23 06:14 UTCVendor advisory
  56. 2026-09-23 06:14 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  57. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  58. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  59. 2026-09-18 05:47 UTCEchelonGraph re-scored
  60. 2026-09-18 05:47 UTCVendor advisory
  61. 2026-09-18 05:47 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  62. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  63. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  64. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  65. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  66. 2026-09-13 23:51 UTCEchelonGraph re-scored
  67. 2026-09-13 23:51 UTCVendor advisory
  68. 2026-09-13 23:51 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  69. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  70. 2026-09-13 08:27 UTCVendor advisory
  71. 2026-09-13 08:27 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  72. 2026-09-12 16:45 UTCEchelonGraph re-scored
  73. 2026-09-12 16:45 UTCVendor advisory
  74. 2026-09-12 16:45 UTCGHSA enrichmentGHSA-4gcc-rqqq-58jp · GitHub severity CRITICAL · GitHub CVSS 7.8
  75. 2026-09-12 03:39 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-56000?
CVE-2026-56000 is a high-severity vulnerability; its CVE record was published on July 8, 2026. 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.
When was CVE-2026-56000 made public?
CVE-2026-56000 was made public on July 8, 2026: that is the date its CVE record's CNA, SUSE, gives for when the vulnerability was made public. The CVE record itself was published on July 8, 2026. EchelonGraph's copy of the record carries a last-modified date of July 9, 2026; the record at its source may have been updated since.
Is CVE-2026-56000 actively exploited?
CVE-2026-56000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56000?
CVE-2026-56000 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-56000?
A fix for CVE-2026-56000 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56000 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56000

Explore →

Is Your Infrastructure Affected by CVE-2026-56000?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.