CVE-2026-97631: managing the residual risk of network boot
Network boot is often enabled for a short operational reason and then left available long after the reason disappears. CVE-2026-97631 makes that residual configuration important. The EDK II vulnerability can be triggered only during PXE startup, but that is exactly when normal endpoint controls are least able to observe the machine.
Vulnerability overview
TianoCore published GHSA-99cj-7hg9-mp4m on October 22, 2026 for a critical EDK II PXE Base Code driver flaw. The affected driver is NetworkPkg/UefiPxeBcDxe, and the advisory assigns CVSS v4 9.5.
EDK II master as of September 14, 2026 is listed as affected. NetApp reports that EDK II through edk2-stable202608 is susceptible. Those are upstream and downstream scope statements, not a complete list of vulnerable hardware.
Mechanism and exploitation conditions
The driver keeps an ICMP error receive request open while PXE is active. It copies messages into a fixed 504-byte field and mishandles both the field boundary and the destination offset. An oversized ICMP message can write attacker-controlled bytes into adjacent memory.
The attacker needs to send a unicast ICMP error to the client's IP during PXE boot. The source advisory says the attack can work over IPv4 or IPv6 and is not limited to the boot server's network location. The exposure interval is the duration of the PXE process.
A malformed packet can cause a CPU exception and stop the boot. A more deliberate packet can create a counterfeit event that DXE dispatches if the attacker knows the target firmware build. That outcome reaches high privilege before the operating system is available.
Impact
The immediate risk is disruption of automated provisioning and recovery. The deeper risk is loss of assurance in the early boot path. An affected system might fail visibly, or it might produce a successful boot whose pre-OS state cannot be reconstructed from ordinary logs.
That uncertainty affects incident response. Rebuilding an operating system does not necessarily correct malicious state in firmware or in the boot environment. Investigators need firmware identity, boot measurements where available, console evidence, and network records from the provisioning window.
Affected products and scope
The relevant scope includes physical servers, appliances, virtual machine firmware, and recovery infrastructure built from EDK II. AMI, Insyde, Phoenix, Project Mu, and other vendors may incorporate the code, but each product needs its own affected-version and fixed-version statement.
Inventory should distinguish between systems that cannot PXE, systems that can enable it, and systems that currently permit it. The middle group is easy to miss because a disabled setting can be changed by a technician, automation error, or recovery procedure.
Exposure context
ZoomEye Search app="AMI" returned 16,445 product fingerprints. The Filter vul.cve="CVE-2026-97631" returned 0. Exposure is 16,445 under the selected result.
This count represents public AMI-related product fingerprints. It does not prove vulnerable firmware, PXE state, or reachability. Its role is to prompt reconciliation with internal ownership and to show where broad vendor visibility exists outside the inventory.
Remediation and mitigations
Apply a fixed firmware image containing TianoCore's corrected boundary and offset logic. Verify it after reboot, and update virtual firmware and recovery media. Where the vendor has not released a fix, use a time-limited PXE prohibition or a tightly controlled provisioning network.
Restrict ICMP to booting clients on the deployment segment. Permit DHCP and boot services only from approved infrastructure. Log boot failures and changes to PXE policy. Review residual exceptions after every recovery or imaging event.
No reviewed source confirmed exploitation in the wild. The remaining risk is still worth managing because the attack window sits below the operating system, the vulnerable code is broadly reusable, and a public fix allows attackers to study the exact parser conditions.
Top comments (0)