CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVE-2026-66801 Microsoft Xbox Remote Code Execution Vulnerability
Critical (9.8) in microsoft microsoft gdk. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.
On this page
Heap-based buffer overflow in Xbox allows an unauthorized attacker to execute code over a network.
Severity
- EPSS
- 1.1% estimated probability of exploitation activity in the next 30 days; 67th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-122 Heap-based Buffer Overflow
- Published
- Modified
- Assigned by
- microsoft (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-66801 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-66801?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-66801?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-66801 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-66801)
HTML:
<a href="https://cve.bz/cve/CVE-2026-66801"><img src="https://cve.bz/cve/badge/CVE-2026-66801.svg" alt="CVE-2026-66801"></a>
Affected
- microsoft:microsoft gdk
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Microsoft GDK | from 1.0.0.0 before 2610 |
Red Hat
Red Hat rates this Critical.
Critical: The default Strimzi transport in Multicluster Global Hub is vulnerable to privilege escalation. A compromised managed hub can exploit weak Kafka Write ACLs on the shared `gh-spec` topic and spoofed CloudEvent sources to gain cluster-admin privileges across the entire fleet of managed hubs. This allows an attacker to achieve fleet-wide administrative control from a single compromised leaf hub.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Multicluster Global Hub 1.4.9 | multicluster-globalhub/multicluster-globalhub-rhel9-operator:1786621416 | Fixed 2026-08-17 | RHSA-2026:55810 |
| Multicluster Global Hub 1.5.8 | multicluster-globalhub/multicluster-globalhub-rhel9-operator:1786621343 | Fixed 2026-08-13 | RHSA-2026:54577 |
| Multicluster Global Hub 1.6.6 | multicluster-globalhub/multicluster-globalhub-rhel9-operator:1786071343 | Fixed 2026-08-12 | RHSA-2026:54392 |
| Multicluster Global Hub 1.7.3 | multicluster-globalhub/multicluster-globalhub-rhel9-operator:1785773214 | Fixed 2026-08-11 | RHSA-2026:53530 |
| Multicluster Global Hub 1.8.2 | multicluster-globalhub/multicluster-globalhub-rhel9-operator:1786067967 | Fixed 2026-08-10 | RHSA-2026:52946 |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-66801.
Attack patterns (CAPEC)
- CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.