Two critical NGINX HTTP/2 flaws allow unauthenticated remote code execution
Several research teams independently found two critical vulnerabilities in the NGINX web server that let attackers run code without authentication. F5 has released security updates; until patched, HTTP/2 should be disabled.
Cybersecurity firm Wiz, together with teams at Ikotas Labs, Metnir, Rapid7 and Xint, independently discovered two critical vulnerabilities in NGINX, a widely used open-source web server that receives traffic and routes it to websites and APIs. The flaws let an attacker execute code on the server remotely without authentication. F5, the company behind NGINX, issued a security release and coordinated public disclosure on November 18.
The issues are tracked as CVE-2026-123633 and CVE-2026-123007, and both are rated Critical with a CVSS 4.0 score of 9.2. Exploitation requires HTTP/2 to be enabled on the server. NGINX powers more than 225 million websites, so one vulnerable deployment can put several services at risk. The bugs are in NGINX itself, so sites can be exposed even when their application code is secure.
The flaws
CVE-2026-123633 is a use-after-free: a connection's memory is released while a request still needs it. It affects reverse-proxy processing when available connection slots run low. CVE-2026-123007 is an integer underflow in flow-control accounting that leads to an invalid memory copy. It affects versions dating back to NGINX 1.9.5 from 2015, and Wiz demonstrated it on a server serving ordinary static files. The use-after-free had been in the code for nearly six years.
Wiz says ASLR, a common memory-safety protection, does not stop these attacks because an attacker can read memory before running code. The company argues that AI is lowering the barrier to finding such complex memory-safety bugs.
What to do
Fixes are available in NGINX OSS 1.30.7 (stable) and 1.31.9 (mainline), as well as in NGINX Plus. If upgrading is not immediately possible, HTTP/2 should be temporarily disabled: on NGINX 1.25.1 or later, set "http2 off;" in affected server blocks, reload NGINX and re-enable the protocol after upgrading. Wiz also advises investigating unexpected NGINX worker crashes or commands launched by NGINX.


