Skip to content
Bora Haber
Markets
  • US dollar50.44up 0.05%
  • Euro55.34down 0.18%
  • British pound66.55down 0.11%
  • BIST 10011,477down 3.08%
  • Gold (gram)6,041down 3.55%
  • Gold (ounce)US$3,725down 3.6%
  • BitcoinUS$62,686down 1.61%
BREAKING

UEFI flaw CVE-2026-97631 puts servers that use PXE network boot at risk

A buffer overflow in the PXE driver of EDK II-based UEFI firmware opens a door for attackers on the local network. A patch is out, but reaching devices will take months.

Arda Sinyal

· 2 min read

Row of server racks with dark perforated doors; red and blue network cables are visible on the left rack.
Rows of data center server racks (representative image, not the incident itself). Temsili görsel · Fotoğraf: Brett Sayles / Pexels

A new security flaw tracked as CVE-2026-97631 has emerged in the PXE driver of UEFI firmware. UEFI is the basic software that runs before the operating system when a device starts, so a weakness here affects the lowest layer of the system. To exploit it, an attacker needs access to the local network.

How the flaw works

The problem lies in the part of the PXE driver that handles ICMP messages. PXE is a method that lets a device load its operating system over the network rather than from a disk. When an unusually long ICMP message arrives during network boot, a 504-byte buffer overflow occurs.

A buffer overflow means data is written outside the space allocated for it. Here the overflowing data exceeds the driver's context structure, letting an attacker write to an area beyond it. The obstacle is that the exact address space of the target firmware must be known. A prepared attacker can still overcome it.

A successful attack could break the chain of trust and could also gain access to the TPM, the security chip. This raises the possibility that disk encryption keys could be exposed.

A very wide area is affected

EDK II is regarded as the reference implementation of UEFI. Nearly all server hardware makers, including AMI, Insyde and Phoenix, use this framework, and cloud providers rely on the same structure. The flaw therefore concerns a very wide area. Only systems that use PXE network boot are affected; home computers that boot from disk are not at risk.

Early disclosure and the patch

Researchers had planned a coordinated disclosure for January 2027. However, AMI published a pull request containing a detailed description of the flaw and its fix ahead of schedule. The TianoCore Project then released an official security advisory. The patch is therefore now available.

Even so, updating firmware on millions of devices will take months. According to experts, the flaw could become a kind of “immortal” vulnerability because it can persist for years on older hardware. While waiting for manufacturers' updates, system administrators can keep PXE boot disabled.

Technology guides

Take a quiz, vote in a poll

Video news

Comments

Sign in to comment.

More on this topic

See all