Reported exploitation of TianoCore EDK2 buffer overflow
Remote firmware bug, patch now ·
In this episode
The facts
- Attackers are reported to be exploiting CVE-2026-97631.
- A fix is available for TianoCore EDK II.
- CVE-2026-97631 is a flaw in TianoCore EDK2.
- CVE-2026-97631 is classed as buffer overflow (CWE-120).
- According to its CVSS rating, CVE-2026-97631 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system. Its impact can reach beyond the vulnerable component.
- CVE-2026-97631 is rated 9.5 out of 10 on the CVSS severity scale.
- FIRST's EPSS model puts the chance that CVE-2026-97631 is exploited in the next 30 days at 0.4 percent.
Sources
The panel
Jordan Pike AI host
CVE-2026-97631 is a buffer overflow (CWE-120) in TianoCore EDK2, rated 9.5 on the CVSS scale. The CVSS rating says it can be exploited remotely over the network, without credentials or user interaction, and a successful attack would fully compromise confidentiality, integrity and availability, with impact that can reach beyond the vulnerable component.
Jordan Pike AI host
Ars Technica reports that attackers are exploiting CVE-2026-97631, which has not been confirmed, and that a fix is available for TianoCore EDK II.
Jordan Pike AI host
FIRST’s EPSS model puts the chance of exploitation in the next 30 days at 0.4 percent.
Maya Okafor AI analyst
A buffer overflow in firmware code like EDK II is a classic case of unsafe memory handling, where data is copied without proper bounds checks. In low-level firmware this often happens because legacy code wasn’t hardened for today’s threat landscape. The CVSS details mean an attacker can remotely gain full control of the device, compromising confidentiality, integrity and availability. The prudent step is to apply the available patch, verify that it removes the vulnerable copy, and scan the same module for any similar unchecked buffers.
Maya Okafor AI analyst
Bold.
Dex Moreno AI analyst
Because the flaw is remotely exploitable without credentials or user interaction, any internet-facing device running the vulnerable firmware can be reached directly. Gaining code execution at the firmware level gives an attacker a deep foothold, often persisting across reboots. From there they can pivot to the operating system, harvest stored keys, or use the device as a launchpad for lateral movement across the network. Even though FIRST’s EPSS is low, watching for chatter and monitoring exposed devices remains wise.
Dex Moreno AI analyst
A buffer overflow that talks to the internet? That’s the software equivalent of shouting “come in” from the front door.
Sam Kowalski AI analyst
We should assume compromise until logs tell us otherwise, especially given the remote nature of the bug. Hunt by pulling firmware update logs, boot-time messages, and any crash dumps that reference the affected module. Correlate those with network traffic to the device’s management interface for unexpected connections. If you find signs of abuse, isolate the device until the patch is applied and the root cause is verified.
Sam Kowalski AI analyst
If your logs were a gym, they’d be full of dead weight.
Rina Takahashi AI analyst
The only attribution we have is the Ars Technica report; no threat-actor claim has been published. Remote, unauthenticated firmware overflows have been used by both nation-state and criminal groups in the past, so the technique is not unique to any single actor. Keep an eye on intel feeds for any mention of CVE-2026-97631 or similar EDK II exploits and add the vulnerability to your watchlist. For internet-facing systems, consider treating it as a KEV-type emergency and prioritize remediation.
Rina Takahashi AI analyst
Attribution is like a game of telephone—everyone’s guessing who shouted first.
Jordan Pike AI host
So you heard it: a high-severity, remotely exploitable firmware bug with a fix already out. Patch exposed systems within 72 hours, per our emergency guidance, and keep an eye on logs and threat-intel feeds for any signs of abuse. That’s your Monday.