Security AffairsPierluigi Paganini
A 16-year-old UEFI flaw puts server firmware at risk
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. This article, 2nd of 2.
CVE-2026-97631 is a critical, 16-year-old vulnerability in the UEFI firmware commonly used to boot servers. The flaw resides in the PXE-Base Code driver (NetworkPkg/UefiPxeBcDxe) within the TianoCore EDK II open‑source project, which is used by hardware makers and cloud providers to build UEFI firmware and is present in major vendors such as AMI, Insyde and Phoenix.
The advisory notes an out-of-bounds write, a classic buffer overflow and incorrect calculation of buffer size in the driver’s handling of ICMP error messages during PXE boot. Exploitation can allow arbitrary code execution before the operating system loads and before Secure Boot or measured boot have verified components, potentially compromising confidentiality, integrity and availability.
The attack would require an attacker with local network access who can inject ICMP errors during PXE boot; this could come from an insider or an attacker who already has foothold on the target network. The CVSS is stated as 9.5/10. The advisory explains that the vulnerable 504-byte field, Mode[.]IcmpError, is written past its bound when longer ICMP messages arrive, enabling code execution in the DXE phase before security protections are active.
While there is no evidence the flaw enables initial network access from outside, it could enable an attacker to install other components that run at riskier privileges. AMI published a fix last month, and Tianocore issued a public warning; Intel and Arm say their products are not directly affected, though vendors may ship vulnerable code.
Organisations are advised to contact firmware suppliers, disable network boot where possible, and monitor logs, noting that TPM and Secure Boot offer limited protection against this vector.
How the story developed
2 articles from 2 outlets since 27 Oct. Still developing; the latest report was 1 hour ago. This was the 2nd report, 15 hours 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. This article, 2nd of 2.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 2 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 11
- A 16-year-old UEFI flaw puts server firmware at risk12:30 · Security Affairs · This article, 2nd of 2