NGINX Patches Two Critical HTTP/2 Flaws That Allow Remote Takeover
F5 released fixes on November 18 for two NGINX bugs that let an unauthenticated attacker run code on a server with HTTP/2 enabled. One of the flaws has been in the code since 2015.
Published 3 min read

NGINX, the open-source web server that sits in front of a huge share of the internet, has two critical bugs that can let an attacker take over a server without logging in. F5, which maintains NGINX, shipped fixes on November 18, and the researchers who reported the flaws are urging administrators to update right away. The catch is that one of the bugs works in a default configuration, and it has been hiding in the code for more than a decade.
The two issues are tracked as CVE-2026-123633 and CVE-2026-123007. Both are memory handling errors in NGINX's HTTP/2 code, and both carry a CVSS 4.0 score of 9.2, which puts them in the critical range. Wiz Research detailed both flaws in a write-up published the same day as the patches.
What the two bugs do
CVE-2026-123007 is an integer underflow in how NGINX tracks the HTTP/2 send window, the counter that controls how much data can be sent before the other side asks for more. According to Wiz, incorrect flow-control accounting pushes that counter past its maximum, an unsigned bounds check wraps around, and NGINX ends up copying memory it should not touch in the TLS send path. The bug affects versions 1.9.5 through 1.31.8, which means it dates back to 2015. Wiz says it is exploitable in default configurations, and that ordinary static files can reach the vulnerable code without any backend application or third-party module.
CVE-2026-123633 is a use-after-free. NGINX can mark an HTTP/2 connection as reusable while a request on it is still active. When the server later closes that connection to free up slots, the request keeps using memory that has already been released. This one needs a narrower setup: HTTP/2 has to be enabled, NGINX has to be working as a proxy, and the server has to be running low on available connections. It affects versions 1.19.7 through 1.31.8, so it has been present for nearly six years.
In both cases, a successful attack runs code with the privileges of the NGINX worker process. Wiz says it confirmed remote code execution, including a bypass of address space layout randomization, on official NGINX 1.31.7 and 1.31.8 builds. The company says it will not release its exploits for now.
Five teams found the same bugs
Wiz was not alone. The company says Ikotas Labs, Metnir, Rapid7 and Xint each found the issues independently. Wiz used its own code-scanning system, Atlas, to find both bugs and validated their impact with AI models. Its timeline shows the first report going to F5 on October 21, with F5 replying that another team had already flagged it.
The scale is what makes the disclosure notable. Wiz cites Netcraft's September 2026 survey, which puts NGINX on more than 225 million websites. Not every one of those sites is exposed, since the attack requires HTTP/2, but HTTP/2 is widely enabled on public servers.
What administrators should do
The fixed releases are NGINX Open Source 1.30.7 on the stable branch and 1.31.9 on the mainline branch. NGINX Plus users need 37.0.8.1 or 37.3.0.1 for the send window bug and 37.0.7.1 or 37.2.0.1 for the use-after-free. The same release also fixes several other memory safety bugs, including one in HTTP/3 and one in the DNS resolver.
For servers that cannot be upgraded right away, Wiz recommends turning HTTP/2 off. On NGINX 1.25.1 and later that means setting http2 off; in the affected server blocks and removing the http2 parameter from listen directives, then reloading and making sure the old worker processes have exited. HTTP/2 can be switched back on after the upgrade.
Wiz also notes that a CDN or web application firewall that terminates HTTP/2 in front of NGINX may blunt some attacks, depending on how it is built. It is not a substitute for patching. Server-side bugs have had a busy month: earlier this week we covered an 11-year-old Linux kernel bug that can crash servers before login.