CVSS 4.0
9.5 criticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCritical (9.5) in tianocore edk2. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExplain CVE-2026-97631 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97631?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97631?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-97631 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| TianoCore EDK2 | through edk2-stable202608 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | edk2 | no fix listed | DEBIAN-CVE-2026-97631 |
| Ubuntu | 22.04:LTS, 24.04:LTS, Pro:16.04:LTS and 2 more | edk2 | no fix listed | UBUNTU-CVE-2026-97631 |
| Ubuntu | 26.04:LTS, 26.10 | edk2, edk2-hwe | no fix listed | UBUNTU-CVE-2026-97631 |
| Red Hat | enterprise_linux:10.2 | edk2, edk2-ovmf, edk2-tools and 4 more | 0:20251114-5.el10_2.3 | RHSA-2026:96240 |
| AlmaLinux | 10 | edk2-ovmf, edk2-aarch64, edk2-tools-doc | 20251114-5.el10_2.3.alma.1 | ALSA-2026:96240 |
| Rocky Linux | 10 | edk2 | 0:20251114-5.el10_2.3 | RLSA-2026:96240 |
| Azure Linux | 3 | edk2 | 20240524git3e722403cd16-22 | AZL-111944 |
| Azure Linux | 3 | qemu | no fix listed | AZL-112172 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.
Red Hat rates this Critical.
This vulnerability is rated as Critical because an unauthenticated network attacker can execute arbitrary code within the pre-boot firmware execution environment without prior access privileges or user interaction. In Red Hat Enterprise Linux and OpenShift environments, EDK2 provides UEFI firmware for virtualized guests. The vulnerability is exposed exclusively during network boot sequences when the PXE driver processes untrusted network packets before the operating system initializes. Virtual machines booting strictly from local storage or operating in their normal post-boot runtime are not exposed to this flaw.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | edk2 | Affected | |
| Red Hat Enterprise Linux 8 | edk2 | Affected | |
| Red Hat Enterprise Linux 9 | edk2 | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Affected |
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-97631.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-120 (13).