F5 Fixes NGINX Flaws Allowing Remote Code Execution
Two memory corruption flaws in NGINX's HTTP/2 code, each rated 9.2 under CVSS 4.0, let an unauthenticated attacker run code in a server worker process, and one of them has been in the software since 2015.
Edited and fact-checked by Stephen Sprague
F5 shipped the fixes in NGINX Open Source 1.30.7 and 1.31.9 on November 18, 2026.
F5 published fixes on Wednesday, November 18, 2026, for two NGINX flaws that let a remote attacker run code without logging in, and both flaws sit in the HTTP/2 code of the web server software. Each one carries a severity score of 9.2 under CVSS 4.0.
The older flaw, CVE-2026-123007, is an integer underflow in HTTP/2 flow control accounting, and F5's advisory describes the defect plainly, saying the flow control window can exceed the allowed threshold. The corrupted accounting can push a worker process into unsafe memory operations, and the vulnerable code shipped in NGINX 1.9.5 in 2015, so every open source release from 1.9.5 through 1.31.8 carries it when HTTP/2 is enabled.
The second flaw, CVE-2026-123633, is a use-after-free bug in the same protocol code, present from NGINX 1.19.7 through 1.31.8, and a server has to accept HTTP/2 connections from clients to be exposed to either flaw. No account or credential is part of the attack path, and successful exploitation runs code inside the NGINX worker process.
Rapid7 researcher Stephen Fewer found the flow control flaw independently, and Rapid7 has published a proof of concept for it, while researchers at Xint, Wiz, Metnir and Ikotas Labs are credited across the two disclosures. No finder or vendor has reported attacks using either flaw in production, and neither flaw appeared in CISA's Known Exploited Vulnerabilities catalog at the time of the disclosure.
The exposure is wide because the software is everywhere, and Netcraft counted more than 225 million sites using NGINX in its September 2026 web server survey. F5 fixed both flaws in NGINX Open Source 1.30.7 on the stable branch and 1.31.9 on the mainline branch, and administrators who cannot upgrade immediately can cut the attack path by disabling HTTP/2 until the patched build is in.
The conversation.
Loading comments…
A little more perspective.
Reading is free. Verified members can comment and reply for $2 a month.