Critical EDK II Firmware Vulnerability Discovered

A severe security flaw in open-source EDK II software allows remote attackers to execute code before an operating system loads.

Updated on Oct. 28, 2026 in Cybersecurity

Critical EDK II Firmware Vulnerability Discovered

Live Poll

Do you trust that tech companies adequately protect your devices against newly discovered security flaws?

Researchers have identified a critical vulnerability in the EDK II network boot driver that permits unauthorized remote code execution. The flaw grants attackers the highest level of system privileges during the pre-boot phase.

Why it matters

The vulnerability poses a significant risk to servers, desktops, and laptops that utilize network booting. Because the flaw allows code execution before the operating system starts, it bypasses standard security defenses.

The vulnerability, tracked as CVE-2026-97631, stems from a failure in the UefiPxeBcDxe driver to enforce size limits on ICMP error messages. It involves a buffer copy process into a 504-byte field.

The players

Alex Matrosov

He is a security researcher who discovered the critical EDK II firmware bug.

Dan Holmes-Mitra

He is a security researcher who collaborated on the identification of this vulnerability.

The details

An attacker can exploit the flaw by sending a single ICMP error message to a client IP address during the network boot process. The driver incorrectly advances the write position during copying, enabling the execution of malicious code.

Timeline

  1. September 14, 2026: EDK II master package listed in the security advisory.

  2. October 15, 2026: Maintainers merged the fix into the public code.

  3. October 22, 2026: Security advisory for the vulnerability was published.

The Tech Race

This discovery highlights the ongoing vulnerability of foundational firmware components that predate the operating system. It underscores the transition from software-based security to a focus on protecting the earliest stages of the hardware boot cycle.

System administrators and users who rely on network booting should monitor their hardware manufacturer for incoming firmware updates to mitigate this risk. Installing these patches is essential to prevent potential unauthorized access to systems.

The takeaway

Users should prioritize hardware security updates as soon as they become available from their device manufacturers. Verifying the integrity of pre-boot processes is a critical step in maintaining modern device security.

Further reading

For broader trends in industry security disclosures, visit the Cybersecurity section.

Live Poll

Do you trust that tech companies adequately protect your devices against newly discovered security flaws?