Trusence Every claim has a source
Last updated 17 November 2026 Search Türkçe
Security

Firmware flaw in EDK II PXE code rated 9.5 out of 10 needs vendor updates

Operators who do not need network boot can turn PXE off while they wait for their firmware vendors to ship a fixed build.

Updated 29 October 2026

A cracked brick in a wall beside a key left in a lock, with a closed gate across the path behind them.
AI-generated illustration

A 16-year-old buffer overflow in the PXE network-boot code of TianoCore EDK II, tracked as CVE-2026-97631 and rated 9.5 out of 10, can let an attacker reach the firmware before Secure Boot checks run, but only while a machine is booting over the network. The flawed copy loop, which lacks a 504-byte limit on ICMP error messages in both IPv4 and IPv6 paths, has been present since 2010, and EDK II is the reference code behind most UEFI firmware from vendors such as AMI, Insyde and Phoenix. A fix is in the EDK II main branch and Microsoft's Project Mu has shipped it in tagged builds, but no stable EDK II release contains it yet, so server operators must wait for firmware updates from their vendors. Because the flaw was publicly described in a pull request before the planned coordinated disclosure date, TianoCore issued its advisory early, and operators who do not need PXE can disable it in the meantime.

Why it matters

The flaw has existed since a November 2010 commit and sits in reference firmware code, so machines running affected builds stay exposed until vendors ship updates. Because the issue was described publicly before the planned coordinated disclosure date, the window for users to act has narrowed. Until updates arrive, the practical change is that anyone who does not rely on network boot should disable that feature.

Sources · 3