Code-execution flaw in UEFI firmware affects most servers on planet Earth

by | Nov 18, 2026 | Technology

Code-execution flaw in UEFI firmware affects most servers on planet Earth

Security researchers have identified a critical code-execution vulnerability in TianoCore EDK II, an open-source firmware codebase used by virtually all major UEFI suppliers to create boot-time firmware for servers and data centers globally. The flaw, designated CVE-2026-97631 and rated 9.5 out of 10 in severity, resides in the ICMP component of the network stack and allows attackers to execute malicious code early in the boot sequence, before operating systems and firmware security mechanisms can be activated.

The vulnerability stems from a 16-year-old buffer overflow in the PXE-Base Code driver, which handles network booting for servers and storage equipment. The driver fails to properly enforce a memory copy limit of 504 bytes when processing ICMP error messages, allowing attackers to overwrite adjacent data with attacker-controlled bytes. An adversary with low-level local network access or a malicious insider can send a crafted error message during the pre-execution environment boot to trigger the flaw. The resulting code execution occurs at ring 0, the CPU’s most privileged execution level, and bypasses attestation processes designed to verify hardware security.

Researchers from Anthropic and Google discovered the vulnerability and had coordinated a disclosure planned for January. However, AMI published a pull request detailing the flaw and its fix earlier, triggering an unplanned public advisory from TianoCore Project members last week. With patch code now publicly available, security experts warn that advanced attackers can easily reverse-engineer exploitation techniques. The vulnerability affects essentially all UEFI suppliers, including AMI, Insyde, and Phoenix, as well as Microsoft’s hardened EDK2 fork known as Project Mu.

Exploitation requires some level of local network control, though attackers can send malicious messages through simple unicast from any network distance to a target device’s IP address during the PXE boot sequence. The resulting payloads lack persistence but create opportunities to install additional malicious components that execute with each boot. Experts note that patching UEFI vulnerabilities across millions of deployed devices from thousands of hardware makers and cloud providers presents significant practical challenges, and the flaw will likely persist indefinitely in end-of-support systems.

Article Attribution | Read More at Article Source

Article summary produced by Claude AI