SecurityOnlineDo Son
EDK II PXE flaw enables remote code execution before boot
Part of the CVE-2026-97631 story · since 27 Oct
- Tue 27 Oct, 21:00 UTC. Ars Technica, first report. UEFI flaw exposes servers to code execution before boot.
- Wed 28 Oct, 12:30 UTC. Security Affairs, its first report on the story. A 16-year-old UEFI flaw puts server firmware at risk.
- Wed 28 Oct, 15:00 UTC. The Hacker News, its first report on the story. UEFI flaw lets attackers run code before Secure Boot on servers.
- Thu 29 Oct, 02:00 UTC. SecurityOnline, its first report on the story. EDK II PXE flaw enables remote code execution before boot. This article, 4th of 4.
The article reports a critical pre-boot remote code execution vulnerability in the TianoCore EDK II PXE driver, tracked as CVE-2026-97631. Discovered by Alex Matrosov of Anthropic and Dan Holmes-Mitra of Google, the flaw scores 9.5 on CVSS v4.0. It affects NetworkPkg in the EDK II master branch as of 14 September 2026, with no official stable release yet marked as patched in the advisory metadata.
The issue allows unauthenticated network attackers to execute arbitrary code during network boot before the operating system loads, potentially granting ring-0 access in the DXE phase and bypassing Secure Boot or measured boot verification.
The vulnerability stems from an out-of-bounds write in the PXE Base Code driver (NetworkPkg/UefiPxeBcDxe). While handling ICMP error messages during IPv4 or IPv6 network boot, the driver maintains a fixed 504-byte buffer (Mode[.]IcmpError) and copies incoming packets without correct per-fragment length checks in the PxeBcIcmpErrorDpcHandle and PxeBcIcmp6ErrorDpcHandle paths.
When a unicast ICMP error message exceeds 504 bytes, data is copied past the buffer, allowing an attacker to plant a counterfeit event so CoreSignalEvent() dispatches arbitrary code in DXE. The article notes there is no public proof-of-concept exploit and no confirmed exploitation in the wild. Mitigations include applying the patch from GitHub pull request #13302 and, for administrators, disabling PXE on untrusted networks or isolating provisioning VLANs. The advisory maintains that there is no patched official stable release and that the impact is a pre-boot remote code execution in the PXE driver.
How the story developed
4 articles from 4 outlets since 27 Oct. Still developing; the latest report was 1 hour ago. This was the 4th report, 1 day after the first.
- Tue 27 Oct, 21:00 UTC. Ars Technica, first report. UEFI flaw exposes servers to code execution before boot.
- Wed 28 Oct, 12:30 UTC. Security Affairs, its first report on the story. A 16-year-old UEFI flaw puts server firmware at risk.
- Wed 28 Oct, 15:00 UTC. The Hacker News, its first report on the story. UEFI flaw lets attackers run code before Secure Boot on servers.
- Thu 29 Oct, 02:00 UTC. SecurityOnline, its first report on the story. EDK II PXE flaw enables remote code execution before boot. This article, 4th of 4.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 4 articles as a listHide the list
- Tue 27 OctDay 01
- UEFI flaw exposes servers to code execution before boot21:00 · Ars Technica · First report
- Wed 28 OctDay 12
- A 16-year-old UEFI flaw puts server firmware at risk12:30 · Security Affairs
- UEFI flaw lets attackers run code before Secure Boot on servers15:00 · The Hacker News
- Thu 29 OctDay 21
- EDK II PXE flaw enables remote code execution before boot02:00 · SecurityOnline · This article, 4th of 4