nginx is a web server that does several jobs at once: it takes requests from the browser, it can sit as a reverse proxy in front of your app, cache content, spread load across several servers, and carry mail. It stands in front of a large share of the world's websites, often without anyone thinking about it until it breaks.
On November 18, 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx. Five of them, detailed by the Xint research team under the name nginx2root, are memory corruption flaws. An unauthenticated attacker can crash a worker process or, per Xint's research, run commands on the server. Xint also found a Linux kernel bug that turns that foothold into root on the host, including from inside a Docker container.
Stopping the attack's frames on the way is one thing. Plugging the code that waits for them is another.
The worst of the five needs no password, only HTTP/2 turned on, and it is commonly enabled on TLS deployments. It has been in every nginx release since 1.9.5. That is why the scale is what it is: Xint found 56.7 million hosts matching nginx on Shodan on November 10, and of the 11.94 million that reported a version, 98.9% fell in the affected range. As of November 19, Censys counts about 8.8 million services running an affected version with HTTP/2 enabled.
The fix is nginx 1.30.7 or 1.31.9, or your vendor's fixed build, plus a restart. As of November 19, none of the five bugs is in CISA's Known Exploited Vulnerabilities catalog and Cloudflare has not seen reports of exploitation in the wild. That is not a reason to wait.
If your nginx is reachable only through Cloudflare's proxy, attackers cannot reach the vulnerable code paths for the most serious of these bugs. Cloudflare terminates every client HTTP/2 and HTTP/3 connection at its edge and opens a separate connection to your origin, so the attacker's frames never reach your nginx. There is also where the protection stops: the resolver bug is not fully covered and depends on how your config builds proxy_pass, and the mail proxy bug is not covered at all, because Cloudflare's HTTP proxy does not carry mail.
Primary sources
Cloudflare's blogThe visual is generated code-art, no third-party images.