
A code-execution vulnerability has been identified in TianoCore EDK II, an open-source UEFI firmware implementation used by the majority of server vendors and data centers globally. Tracked as CVE-2026-97631 and rated with a severity score of 9.5 out of 10, the flaw enables attackers to execute malicious code early in the boot sequence, bypassing security mechanisms like Secure Boot and Trusted Platform Module protections.
The vulnerability stems from a memory-corruption issue within an ICMP component of the PXE-Base Code driver. The driver fails to properly enforce a 504-byte memory copy limit when processing ICMP error messages during network boot operations, allowing attackers to overwrite adjacent data and corrupt the UEFI module. Exploitation requires some level of local network access but can be delivered via a simple unicast message to a target device’s IP address during the PXE boot sequence. While payloads execute only once without persistence, they can establish a foothold for installing additional malicious components that run with ring 0 privileges on each boot.
The vulnerability was discovered by researchers from Anthropic and Google, who had coordinated a disclosure planned for January. However, AMI published a pull request detailing the flaw and providing a fix last month, which led the TianoCore Project to publicly release an advisory last week. The early public availability of patch code has raised concerns about the ease with which sophisticated threat actors can develop working exploits. Additionally, patching UEFI vulnerabilities across millions of devices sold by thousands of manufacturers presents significant logistical challenges.
This discovery joins a growing list of critical UEFI vulnerabilities, including LogoFail and PixieFail, which similarly allow attackers to subvert the boot-time chain of trust. Security researchers note that exploitation is particularly appealing because it occurs before operating system and firmware defenses are active. The widespread adoption of EDK2 by virtually all UEFI suppliers, including Microsoft’s hardened Project Mu fork, means the impact could affect a substantial portion of the world’s computing infrastructure.
Article Attribution | Read More at Article Source
Article summary produced by Claude AI