Skip to content
major vulnerability· requires attention

EDK2 is upstream UEFI firmware used across servers, workstations and embedded devices; a remote firmware RCE can lead to widespread, persistent compromises.

Hardware

CVE-2026-97631

9.5
Critical
EPSS 0.43%Patch availableOct 24, 2026

Remote buffer overflow in EDK2 UEFI BIOS allows arbitrary code execution.

common questions

Is CVE-2026-97631 being exploited?

Not confirmed. CVE-2026-97631 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.

How severe is CVE-2026-97631?

CVE-2026-97631 is rated Critical with a CVSS score of 9.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-97631?

Yes. A fix has been recorded for CVE-2026-97631. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-97631 affect?

CVE-2026-97631 affects TianoCore EDK2 (UEFI BIOS), Servers, Workstations, Embedded devices using EDK2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-97631?

Install vendor BIOS/UEFI updates immediately; verify firmware integrity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TianoCore EDK2 (UEFI BIOS)ServersWorkstationsEmbedded devices using EDK2
impact

Remote buffer overflow in UEFI (EDK2) enabling arbitrary code execution, full system compromise and firmware-level persistence.

action required

Immediate action required

affected versions
TianoCore EDK2
  • affected<= edk2-stable202608

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved