nginx2root: Five Critical nginx Flaws Let Attackers Run Code — Patch to 1.30.7 or 1.31.9 Now
On 18 November 2026, F5 and nginx.org disclosed ten nginx vulnerabilities. Five of them, published by the Xint research team under the name nginx2root, are memory-corruption flaws that can let an unauthenticated attacker crash a worker process or run code on the server — and Xint chained the worst of them with an unpatched Linux kernel bug to reach root on the host. The fix is nginx 1.30.7 or 1.31.9, and administrators should patch and restart now.
nginx2root: Five Critical nginx Flaws Let Attackers Run Code — Patch to 1.30.7 or 1.31.9 Now
Five critical vulnerabilities in nginx, disclosed on 18 November 2026, can let an attacker who never logs in crash a web server or run their own code inside it. The flaws, published by the Xint research team under the name nginx2root, affect a huge share of the servers running the world's websites — and one of them can be chained with an unpatched Linux kernel bug to take over the whole host. The fix is already out: nginx 1.30.7 on the stable branch and 1.31.9 on mainline. If you run nginx, this is a patch-now event.
nginx is one of the most widely used web servers on the internet, sitting in front of websites as a reverse proxy, load balancer and cache. That reach is what makes this disclosure so serious. Before the announcement, Xint searched Shodan on 10 November and found 56.7 million hosts running nginx. Of the 11.94 million that reported a version number, 98.9 percent fell inside the affected range. Censys counted about 8.8 million services running a potentially affected version with HTTP/2 enabled as of 19 November. Version strings do not prove a host is vulnerable — Linux distributions often backport fixes without changing the reported version — but the exposure is plainly enormous.
What nginx2root is
On 18 November, F5 and nginx.org disclosed ten vulnerabilities in nginx and shipped fixed releases. Five of them were reported by Xint, which published technical details on those five under the name nginx2root. Each is an independent path to memory corruption in a worker process, and each needs a different server configuration to trigger. F5 rates every one of the five as High under CVSS version 3.1, with a score of 8.1, and Critical under CVSS version 4.0, with a score of 9.2. The nginx project itself rates two of them major and the other three medium.
The five flaws are:
| CVE | What it is | Needs this setup | First affected release |
|---|---|---|---|
| CVE-2026-123007 | Integer overflow in HTTP/2 flow control, leading to out-of-bounds heap reads and writes | HTTP/2 enabled | 1.9.5 (2015) |
| CVE-2026-123633 | Use-after-free in HTTP/2 proxying | HTTP/2 with proxy_pass to a backend, worker low on worker_connections | 1.19.7 |
| CVE-2026-121810 | Use-after-free in HTTP/3 (QUIC) proxying | HTTP/3 with proxy_pass to a backend | 1.25.0 |
| CVE-2026-123634 | Use-after-free in the resolver | resolver plus proxy_pass with variables, plus an SSI or mirror subrequest | 0.6.18 |
| CVE-2026-113425 | Use-after-free in the mail proxy | Mail proxy with proxy on and auth_http | 0.5.33 |
CVE-2026-123007 is the one to worry about most. It needs nothing more than HTTP/2 turned on, which is standard on modern TLS deployments, and it has been present in every nginx release since HTTP/2 support shipped in version 1.9.5. It is a miscount in HTTP/2 flow control: an attacker sends a carefully ordered stream of protocol frames — billions of WINDOW_UPDATE frames, SETTINGS frames that hold response data back, PING frames that fill the send buffers, partial HEADERS frames and RST_STREAM at exactly the right moment — and the send-window count overflows, corrupting memory. Xint ran its exploit over the public internet against servers hosted on AWS, Google Cloud and Azure. Wiz Research has demonstrated the same flaw being used to gain remote code execution, complete with a bypass for ASLR, the address randomisation defence, against the official 1.31.7 and 1.31.8 builds.
The other four flaws are narrower but no less real. Two are use-after-free bugs that appear when a worker runs low on connection slots and closes the very connection the request belongs to. The resolver flaw fires when a request and its mirror or SSI subrequest wait on the same DNS lookup and the main request ends while the answer is being processed. The mail proxy flaw can be triggered during login, without valid credentials. Four of the five bugs are use-after-free flaws — a class of memory error where one part of the program frees an object that another part is still using.
The same releases also fix five further nginx vulnerabilities. The most serious of those, CVE-2026-118899, is an infinite loop while reading a request body over TLS 1.3 that lets an unauthenticated attacker stall a worker process, in nginx 1.13.0 and later.
From a web server flaw to root on the host
The name nginx2root comes from the second half of Xint's research. The team also found a use-after-free bug in the Linux kernel's SCTP send path, present since Linux 4.15, released in 2018. While a send operation waits, its SCTP association can be moved to another socket, and the waiting send can then free it. An attacker who already runs code as the nginx worker can use that kernel bug to gain root on the host — and Xint did exactly that from an nginx server running inside a Docker container.
That detail matters because containers are often treated as a safety net. Here, the container did not stop the chain. Many Linux distributions also load the SCTP module automatically the first time a program opens an SCTP socket, so hosts that never use SCTP can still be exposed. As of 18 November, no kernel fix was available, and Xint was withholding the details of the kernel bug until one exists.
Is it being exploited yet?
As of 19 November, none of the five nginx2root CVEs was listed in CISA's Known Exploited Vulnerabilities catalog, and no reports of exploitation in the wild had appeared. That is the good news, and it is also the window to patch in.
Proof-of-concept code is already circulating. Rapid7 published a proof of concept for CVE-2026-123007 on 19 November, which it describes as suitable only for demonstrating the attack against a freshly started local container. Xint and Wiz Research have not released their exploits. Fake exploits are also circulating on GitHub, so administrators should not run anything claiming to be an nginx2root exploit from an untrusted source.
What to do now
The fix is straightforward, and it is the only complete answer. Update nginx Open Source to 1.30.7 or 1.31.9, or NGINX Plus to 37.0.8.1 or 37.3.0.1, or install your Linux distribution's patched package — Debian, Ubuntu and the official Docker image have shipped fixes. Then restart nginx. A configuration reload is not enough, because it does not replace the running binary. F5 lists NGINX Plus releases R34 to R36 as affected with no fixed build, so those should move to a fixed 37.x release.
Before patching, find every nginx server you run: Open Source, Plus, distribution packages, container images and appliances. Run nginx -V and nginx -T on each and note HTTP/2 and HTTP/3 listeners, proxy_pass with variables combined with SSI or mirror, and any mail block. And check backported versions carefully — distributions often patch without changing the version that nginx -v reports, so compare the full package version against your distribution's advisory.
If you cannot patch today, disable what you do not need. Setting http2 off — on nginx 1.25.1 and later, or removing http2 from the listen directive on older versions — blocks CVE-2026-123007 and CVE-2026-123633. Removing QUIC listeners and setting http3 off blocks CVE-2026-121810. Pointing proxy_pass at fixed upstream groups helps against the resolver flaw, and binding mail listeners to trusted networks limits the mail proxy flaw. Restart so old connections close.
For the kernel side of the chain, add install sctp /bin/false to a file in /etc/modprobe.d/ to stop the SCTP module from loading. That is a stopgap, not a fix: it does not unload an already-loaded module, and it does not help if SCTP is built into the kernel. When your distribution ships a kernel update for the SCTP bug, install it and reboot.
Cloudflare users get partial cover — with a catch
Cloudflare says its own edge is not affected: much of the proxy handling customer traffic now runs on FL2, written in Rust, and the parts still built on its heavily modified nginx fork were reviewed against all five bugs, with an update closing the related code paths rolling out globally before the vulnerabilities were published.
Origins sitting behind Cloudflare's HTTP proxy are shielded from the HTTP/2 and HTTP/3 attacks, because Cloudflare terminates every client HTTP/2 and HTTP/3 connection at its edge and opens a separate connection to the origin. The attacker's control frames never reach the origin's nginx. But that protection has a condition: the origin must not be reachable directly. If an attacker can find the origin's IP address and connect to it directly, Cloudflare is not in the path and the protection does not apply. Cloudflare recommends Cloudflare Tunnel, firewalling inbound traffic to Cloudflare's published IP ranges, or Authenticated Origin Pulls.
The protection also stops short of the other two flaws. The resolver vulnerability depends on how the configuration builds its proxy_pass target, and the mail proxy is not carried by Cloudflare's HTTP proxy at all, so neither is fully covered. Cloudflare has not released a WAF rule for these bugs, noting that they are protocol-level flaws and the protection comes from connection termination, not pattern matching. The message is the same either way: patch.
Sources
- Cloudflare Blog — nginx2root: five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them
- Cloudflare Radar, Zero Wire — nginx2root: remote code execution in nginx HTTP/2, HTTP/3, resolver and mail proxy
- Censys — Nov 18 Advisory: NGINX Memory Corruption Vulnerabilities (nginx2root)
- SOCRadar — NGINX2Root: What NGINX Admins Should Know
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0