Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Screenshot of the TianoCore EDK II GitHub security advisory GHSA-99cj-7hg9-mp4m, titled Pre-boot RCE in EDK II PXE driver, marked Critical, listing the NetworkPkg package, affected versions EDK II master as of 2026-09-14, patched versions Not patched currently, and a CVSS v4 base score of 9.5.
Image: TianoCore EDK II project on GitHub (fair use). Advisory GHSA-99cj-7hg9-mp4m, captured Oct. 30, 2026.

Response

A Single Oversized ICMP Error Can Hijack a Machine's Firmware During Network Boot, and No Released EDK II Version Carries the Fix Yet

CVE-2026-97631, rated 9.5, lets an unauthenticated attacker overflow a 504-byte buffer in the EDK II PXE driver and run code before Secure Boot or the operating system loads. The fix is merged in EDK II's development branch, but most machines will need firmware updates from their vendors; until then, the advice is to turn off PXE where it is not needed and fence off provisioning networks.

Noah Park, ResponseNew York5 min read

NEW YORK - A flaw in the network boot code of EDK II, the open source firmware foundation that many server and PC makers build their UEFI firmware on, lets an attacker who can reach a machine while it boots over the network corrupt memory and run code before the operating system, Secure Boot or measured boot gets a chance to check anything, according to the project's security advisory.

The bug, CVE-2026-97631, is in the PXE Base Code driver, NetworkPkg/UefiPxeBcDxe. The TianoCore project rates it Critical, 9.5 under CVSS v4. It was found by Alex Matrosov of Anthropic and Dan Holmes-Mitra of Google, who also supplied the recommended fix, the advisory says.

The fix has landed in EDK II's development branch. It has not yet reached the machines that matter. The advisory, published Oct. 22, lists "Not patched currently" under patched versions, and NetApp's advisory describes EDK II versions through the edk2-stable202608 release as affected. Debian's security tracker on Friday showed every Debian edk2 package, from bookworm through unstable, as vulnerable with no fixed version. For most organizations the remedy will be a BIOS or UEFI update from each hardware vendor, and those are only beginning to appear. NetApp, for one, published an interim advisory on Friday saying it is aware of public discussion of the flaw and will update the advisory as more information becomes available.

One ICMP error, 504 bytes and a bad pointer

Screenshot of the oss-security mailing list post CVE-2026-97631: Pre-boot RCE in EDK II PXE driver, dated Oct. 28, 2026, which copies the TianoCore advisory's summary, details, impact, patch and credit sections.
Image: oss-security mailing list, Openwall (fair use).The Oct. 28, 2026, post copying the TianoCore advisory.

During a network boot, the PXE driver keeps a receive request open for ICMP error messages and copies each one into a fixed 504-byte field, Mode.IcmpError. According to the advisory, the copy loop gets the bounds wrong in both the IPv4 and IPv6 handlers: it keeps copying bytes for a message longer than 504 bytes, and it advances the destination pointer by the cumulative length rather than the length of each fragment. An oversized message therefore writes attacker-controlled bytes past the end of the field, and "nothing earlier on the receive path restricts the message length."

The attacker needs no credentials. "The attacker needs only to deliver a unicast ICMP error message addressed to the client's IP, from any network distance; the exposure window is the duration of the PXE boot," the advisory says.

TianoCore describes two outcomes. The first is deterministic: the driver's private data is corrupted and the next ICMP error triggers a CPU exception inside the DXE core, so the boot hangs, a denial of OS provisioning or recovery. The second requires more knowledge. An attacker who knows the target's firmware build can plant a counterfeit event in the same packet so that CoreSignalEvent() dispatches attacker-supplied bytes in the DXE phase, which the advisory describes as "ring 0, before any OS security control exists."

The fix and who has it

Screenshot of the merged EDK II pull request 13302, titled NetworkPkg/UefiPxeBcDxe: Fix ICMP buffer overflow in IPv4/IPv6 handle (CVE-2026-97631), showing the description of the root cause and the resolution adding boundary checks and corrected buffer offset calculations.
Image: TianoCore EDK II project on GitHub (fair use).Pull request 13302, captured Oct. 30, 2026.

The correction is pull request 13302, merged into the EDK II master branch on Oct. 15. Its description says incorrect buffer copy logic "allowed large packets to write beyond the allocated buffer," and that the change adds boundary checks and corrected offset calculations so oversized ICMP error packets are "safely truncated when the buffer is full." It also zeroes the buffer before copying, so short packets do not leave stale bytes from a previous error.

Because EDK II is a reference codebase rather than a product, firmware vendors have to pull the change into their own builds and ship them. Virtual machines are part of the picture too: the oss-security post notes that Debian lists OVMF, the EDK II firmware used by many QEMU and KVM guests, as vulnerable.

Screenshot of NetApp security advisory NTAP-20261030-0004, CVE-2026-97631 Tianocore EDK2 Vulnerability in NetApp Products, with status Interim, a CVSS v4 score of 9.5 and a reference to the TianoCore advisory.
Image: NetApp (fair use).Interim advisory NTAP-20261030-0004, captured Oct. 30, 2026.

What defenders can do before firmware updates arrive

The exposure window is the network boot itself, so the first job is knowing which machines PXE boot at all: bare-metal provisioning pools, imaging and recovery workflows, diskless and VDI hosts, and virtual machines whose firmware tries the network first. Italy's national CSIRT, in an alert dated Oct. 28, recommends applying vendor firmware updates that include the TianoCore fix and, until they are available, disabling PXE network boot where it is not strictly necessary or limiting it to trusted, properly segregated networks.

For responders, two practical points follow from the advisory. A machine that hangs during a PXE boot after an unexpected ICMP error is worth a second look rather than a reflexive reboot, since the deterministic outcome is a boot hang. And because the code runs before Secure Boot or measured boot has checked any OS component, those controls will not flag a successful attack, so asset inventories and firmware version tracking are the main defense until updates ship. Ask each server, board and appliance vendor whether its firmware is built on EDK II and when an update for CVE-2026-97631 will be available.

About the Author

Noah Park

Noah Park covers incident response and blue-team operations for SOCtember from New York.

Related stories

Response desk