NGINX sits in front of a large share of the web as the TLS terminator, reverse proxy, load balancer and Kubernetes ingress. On November 18, 2026, F5 released nginx 1.31.9 (mainline) and 1.30.7 (stable) together with coordinated disclosures from Xint, Wiz Research, Rapid7, Metnir and Ikotas Labs. Several of these teams found the same bugs independently. Xint grouped five of them under the name NGINX2Root. Sophos and Wiz list each of the five at 9.2 under CVSS 4.0, while nginx.org’s own advisory page uses its usual major/medium labels.
The fix release also addresses several lower-severity issues, including a TLS 1.3 request-body infinite loop (CVE-2026-118899).
The five bugs
| CVE | What it is | What you need to be exposed | Vulnerable (nginx.org) |
|---|---|---|---|
| CVE-2026-123007 | HTTP/2 flow-control integer underflow → invalid memcpy length | HTTP/2 enabled on the listener | 1.9.5–1.31.8 |
| CVE-2026-123633 | HTTP/2 connection use-after-free | HTTP/2 plus proxying to an upstream, with connection slots running low | 1.19.7–1.31.8 |
| CVE-2026-121810 | HTTP/3 (QUIC) use-after-free | HTTP/3 plus proxying to an upstream | 1.25.0–1.31.8 |
| CVE-2026-123634 | Resolver use-after-free during response processing | proxy_pass to a server name with variables, plus an SSI or mirror subrequest that resolves the same name | 0.6.18–1.31.8 |
| CVE-2026-113425 | Mail proxy use-after-free | nginx configured as a mail proxy with auth_http | 0.5.33–1.31.8 |
The bugs are independent. An attacker needs only one exploitable path, not the whole set.
Why CVE-2026-123007 is the one to worry about
HTTP/2 flow control lets the client tell the server how many response bytes it may send. nginx tracks that credit per stream and per connection. Rapid7’s Stephen Fewer found that a client can cancel queued response data and make nginx return credit for bytes it never sent. The counter underflows. A later response is then copied with an invalid length, which corrupts memory in the worker.
What makes this bad:
- The configuration is the default one. You only need
http2on a TLS listener. Wiz demonstrated code execution against nginx serving ordinary static files, with no backend application and no third-party modules. - It’s old. The bug has been in the code since nginx 1.9.5 (2015), when HTTP/2 support arrived. Xint says that as of November 10, 98.9% of hosts with an identifiable nginx version were affected.
- ASLR doesn’t stop it. According to Sophos’s summary of F5’s advisories, code execution needs ASLR to be disabled or bypassed. Wiz and CIRCL point out that the researchers did bypass it, using the same bugs to read memory first.
Exploitation does have practical limits. Rapid7’s proof of concept against the official nginx 1.31.8 Docker image needed about 128 GB of HTTP/2 data. That took two and a half minutes in the lab, about two minutes on a 10 Gbit/s link and about seventeen minutes on 1 Gbit/s. Because nginx closes connections after one hour by default, anything slower than roughly 300 Mbit/s runs out of time. If an intermediary proxy re-frames HTTP/2, the exact frames the exploit depends on probably won’t reach nginx. Rapid7’s technique also relies on a specific glibc AVX-512 memcpy variant. These limits raise the bar, but they don’t remove the risk for well-connected targets.
From worker to root
On its own, each bug gives code execution as the nginx worker process, usually an unprivileged user. Xint went further and chained each one with a separate Linux kernel SCTP use-after-free/double-free (code from Linux 4.15) to bypass KASLR and get root on the host. That included escaping a Docker container, because containers share the host kernel. CIRCL notes that this kernel bug had no CVE ID as of November 18.
Where you don’t need SCTP, CIRCL describes blocking module loading with install sctp /bin/false in modprobe config. That doesn’t unload a module that is already loaded and does nothing if SCTP is built into the kernel.
What to do
- Upgrade NGINX Open Source to 1.31.9 or 1.30.7. For NGINX Plus, Rapid7 lists 37.3.0.1 and 37.0.8.1 as the fixed builds for CVE-2026-123007 and no fix for R34–R36; check the F5 advisories for the other CVEs.
- Restart, don’t just reload. Xint notes that
nginx -s reloaddoes not load the new binary. Confirm that old workers are gone. - Find the hidden copies: ingress controllers, base images, appliances and vendor bundles that ship their own nginx. Distro packages may lag, especially on older releases.
- If you can’t patch today, set
http2 off;on exposed server blocks (nginx 1.25.1+) and removehttp2fromlistendirectives. That blocks CVE-2026-123007 and CVE-2026-123633, but not the HTTP/3, resolver or mail paths. For those, F5 advises avoiding SSI/mirrorwith variable upstream names and keeping mail proxy listeners on trusted networks. - Watch for unexpected worker crashes and child processes spawned by nginx. Wiz says these are general warning signs, not confirmed indicators of compromise.
No in-the-wild exploitation had been reported at disclosure time. Given how many teams found the same bugs, and that Wiz says it used AI models to validate the impact, it would be unwise to assume that stays true for long.