Two critical NGINX2Root flaws can let attackers run code on an unpatched NGINX server without signing in. On November 19, Censys estimated that 8.8 million NGINX services met the initial criteria for potential exposure, though individual servers’ patch status and configuration determine the risk.
Even a server hosting static files can be vulnerable
Wiz demonstrated the first flaw, CVE-2026-123007, on a server that delivered ordinary static files over an encrypted HTTP/2 connection. The vulnerability affects NGINX versions 1.9.5 through 1.31.8, a range that stretches back to 2015. A flaw in HTTP/2 flow control can corrupt memory in the worker process that handles incoming requests.
The second vulnerability, CVE-2026-123633, affects versions 1.19.7 through 1.31.8. It applies to a narrower group of servers because NGINX must also forward requests to a backend. Wiz demonstrated remote code execution through this flaw as well.
Gaining full control of the underlying host required an additional vulnerability in Xint’s demonstration. The researchers combined the first NGINX flaw with a separate Linux kernel bug to escape a container and gain root privileges on the host. In independent tests, Censys reproduced memory corruption in four of the five NGINX flaws under investigation. Its tests stopped short of remote code execution.
Why the exposure estimate has limits
Censys based its estimate of 8.8 million potentially exposed services on two observable details. Each service supported HTTP/2 and reported an NGINX version within the affected range for the first flaw. However, a distributor can apply a security fix to an older release while retaining its version number. Another 104 million services disclosed no version at all, leaving their patch status unclear.
By November 19, Censys had also identified more than 511,000 previously exposed services whose operators had applied a patch or mitigation. For administrators assessing their own sites, the relevant checks include whether the installed package contains the fix and whether an internet-facing listener accepts HTTP/2 connections.
Which releases fix the NGINX2Root flaws?
F5 issued fixes in NGINX Open Source 1.30.7 on the stable branch and 1.31.9 on the mainline branch. For NGINX Plus, the patched releases are 37.0.8.1 and 37.3.0.1. Administrators who need time to upgrade can temporarily disable HTTP/2 to address the two NGINX2Root flaws.
The update also fixes issues in HTTP/3 reverse proxying, DNS resolution and mail proxy authentication. A separate high-severity flaw can cause a worker to loop indefinitely while reading a request over TLS 1.3, disrupting service. Those issues still require attention even if administrators disable HTTP/2.


0 responses to “NGINX2Root flaws expose HTTP/2 servers to takeover”