cve.bz

CVE-2026-97631 tianocore edk2: Classic Buffer Overflow

9.5 criticalEPSS 0.6%

Critical (9.5) in tianocore edk2. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
EDK2 contains a vulnerability in BIOS where a user may cause “Out-of-bounds Write”, Classic Buffer Overflow, and “Incorrect Calculation of Buffer Size” by remote access. Successful exploitation of this vulnerability can lead to arbitrary code execution. It could also impact Confidentiality, Integrity, and Availability.

Severity

CVSS 4.0

9.5 critical
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS
0.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 51st 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: no · Technical impact: total, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-120 Buffer Copy without Checking Size of Input (Classic Buffer Overflow)
CWE-131 Incorrect Calculation of Buffer Size
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
TianoCore EDK2through edk2-stable202608

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14edk2no fix listedDEBIAN-CVE-2026-97631
Ubuntu22.04:LTS, 24.04:LTS, Pro:16.04:LTS and 2 moreedk2no fix listedUBUNTU-CVE-2026-97631
Ubuntu26.04:LTS, 26.10edk2, edk2-hweno fix listedUBUNTU-CVE-2026-97631
Red Hatenterprise_linux:10.2edk2, edk2-ovmf, edk2-tools and 4 more0:20251114-5.el10_2.3RHSA-2026:96240
AlmaLinux10edk2-ovmf, edk2-aarch64, edk2-tools-doc20251114-5.el10_2.3.alma.1ALSA-2026:96240
Rocky Linux10edk20:20251114-5.el10_2.3RLSA-2026:96240
Azure Linux3edk220240524git3e722403cd16-22AZL-111944
Azure Linux3qemuno fix listedAZL-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

Red Hat rates this Critical.

Red Hat's statement

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10edk2Affected
Red Hat Enterprise Linux 8edk2Affected
Red Hat Enterprise Linux 9edk2Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

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.

GitHub PoC

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.

  • Try2Take/CVE-2026-97631-PoC Harbor Check: matches CVE 2 stars, Python, created
    An educational laboratory for studying a PXE network-boot vulnerability in EDK II / OVMF. It builds a pinned EDK II revision, boots a UEFI …
  • slabbdev/uefi-pxe-cve-2026-97631 Harbor Check: matches CVE 1 star, Python, created
  • RayanZiani/Bootjack Harbor Check: matches CVE 0 stars, created
    CVE-2026-97631 C

Attack patterns (CAPEC)

  • CAPEC-47 Buffer Overflow via Parameter Expansion Likelihood: Medium · Severity: High
  • CAPEC-100 Overflow Buffers Likelihood: High · Severity: Very High

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

References

Check your stackJSON