cve.bz

CVE-2026-79608

9.8 criticalEPSS 0.3%

Critical (9.8). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
The workaround for XSA-433 (Zenbleed, CVE-2023-20593) was later re-worked to better integrate with other manipulations of the same MSR. In this rework an inverted conditional was introduced, resulting in the workaround to not be applied when needed and vice versa. For more details, see: http://xenbits.xen.org/xsa/advisory-433.html

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-17. 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-10-20. 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-670 Always-Incorrect Control Flow Implementation
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-79608 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-79608?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-79608?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-79608 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.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13xen4.20.4+39-gf1e1321c87-0+deb13u1DEBIAN-CVE-2026-79608
Debian14xen4.20.4+39-gf1e1321c87-1DEBIAN-CVE-2026-79608
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morexenno fix listedUBUNTU-CVE-2026-79608
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Module for Server Applications 15 SP7xen4.20.4_06-150700.3.49.2SUSE-SU-2026:4942-1
openSUSETumbleweedxen4.22.0_06-1.1openSUSE-SU-2026:12138-1
Alpinev3.21xen4.19.6-r2ALPINE-CVE-2026-79608
Alpinev3.22, v3.23xen4.20.4-r2ALPINE-CVE-2026-79608
Alpinev3.24xen4.21.2-r2ALPINE-CVE-2026-79608

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in Xen. An inverted conditional in the reworked XSA-433 (Zenbleed) workaround causes the mitigation to not be applied when needed. Exploitation requires AMD Zen2 CPUs with out-of-date microcode; a malicious guest can read data from other contexts on the same core. Red Hat does not ship the Xen hypervisor in supported products; the Fedora community package xen 4.20.4 is in the affected range (XSA-515: 4.20.3+).

Red Hat's mitigation

update CPU microcode (firmware or amd-ucode from linux-firmware, Zenbleed fix published late 2023); alternatively disable AVX (cpuid=no-avx or cpuid=host:avx=0 per untrusted VM) with significant performance impact; upstream fix patch xsa515.patch exists.

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-79608.

References

Check your stackJSON