Ten new nginx flaws threaten millions of web servers with remote root takeovers
Researchers revealed critical memory bugs in nginx alongside a Linux kernel flaw. While Cloudflare shields proxied traffic, millions of public servers require immediate patches.
On November 18, 2026, security researchers and vendors disclosed ten vulnerabilities affecting nginx, the web server that powers a vast share of internet infrastructure. Five of these issues, collectively dubbed nginx2root by research team Xint, involve memory corruption flaws. An unauthenticated attacker can use them to crash processes or execute unauthorized commands.
Xint also demonstrated that an attacker who gains control of an nginx worker process can combine it with an unpatched Linux kernelLinux kernelThe core software program that manages computer hardware and acts as a bridge between physical components and applications. Open in glossary bug. This exploit grants full root access to the underlying host, even breaking out from inside a Docker container.
The scope of the nginx2root bugs
The disclosed flaws range across multiple versions of nginx. The most dangerous is CVE-2026-123007, an integer overflowInteger overflowAn error that occurs when a calculation produces a number too large for its assigned memory space. Open in glossary linked to HTTP/2 support that has existed since release 1.9.5 in 2015. F5 assigned the five primary bugs a critical CVSS score of 9.2. Researchers tested the exploit across major cloud platforms including AWS, GCP, and Azure.
Scanning data highlights the potential blast radius. A search on Shodan before the disclosure revealed 56.7 million nginx hosts, with nearly 99% of version-reporting servers falling into vulnerable ranges. Censys later tracked roughly 8.8 million services actively running affected versions with HTTP/2 enabled. The package releases also patch five other issues, such as an infinite loop vulnerability triggered during TLS 1.3 handshakes.
How proxies blunt the attack
Cloudflare confirmed that its edge infrastructure is unaffected. The company updated its remaining modified nginx software before the public disclosure, while much of its core proxy runs on FL2, an internal system written in Rust.
For website operators using Cloudflare’s HTTP proxy, the risk is significantly reduced. Exploiting the HTTP/2 and HTTP/3 flaws requires an attacker to transmit precise, malicious sequences of protocol frames directly to the target machine. Cloudflare terminates connections at its edge, strips low-level client frames, and issues fresh connections to origin servers. Because these malicious instructions are not forwarded, backend servers behind the proxy cannot be triggered by the network attack.
Despite this shield, security teams advise administrators to update origin installations to versions 1.30.7 or 1.31.9 immediately. The proxy does not protect all configurations, such as mail proxy setups or resolver subrequests.
How does this story land?
One tap per reader.
Quick poll
Can cloud proxy shields justify delaying critical server software patches?
One tap. No sign-up.
Ask this story
Still have a question?
Answers use only what is in this story. They are written by AI and can be wrong.