nginx shipped 1.30.7 (stable) and 1.31.9 (mainline) on November 18 to fix ten vulnerabilities. The most serious is CVE-2026-123007, a memory-corruption bug in HTTP/2 flow control that researchers at Xint and Wiz separately turned into unauthenticated remote code execution. F5 rates it 9.2 under CVSS 4.0. Per Xint, every official release since 1.9.5 (2015), when nginx first added HTTP/2, is affected.
Why it matters: nginx is everywhere. It sits in front of websites, APIs, container ingresses and load balancers. Wiz, citing Netcraft, says it powers more than 225 million websites. Xint counted 56.7 million Shodan hosts identifying as nginx. Of the 11.9 million that showed a version, 98.9% fell inside the affected range. Xint stresses that this doesn't make them all vulnerable, because HTTP/2 must be on and distributions backport fixes. Still, a bug in nginx's default HTTP/2 path is about as broad as server-side exposure gets.
What's broken
Xint calls the set "NGINX2Root". It is five bugs, reported to F5 through HackerOne in mid-October:
| CVE | What it is (per Xint/Wiz) | In scope if you use… | Does turning off HTTP/2 help? |
|---|---|---|---|
| CVE-2026-123007 | Integer overflow/underflow in HTTP/2 send window leads to an out-of-bounds heap copy | HTTP/2, even for plain static files | Yes |
| CVE-2026-123633 | Use-after-free in HTTP/2 | HTTP/2 reverse proxying when a worker is low on connections | Yes |
| CVE-2026-123634 | Use-after-free in the resolver | Request-built proxy_pass names plus mirror or SSI |
No |
| CVE-2026-121810 | Use-after-free in HTTP/3 (QUIC) | HTTP/3 with proxying | No |
| CVE-2026-113425 | Use-after-free in the mail proxy | Mail proxy with auth_http |
No |
Xint's write-up explains the main bug. Cancelled streams credit unused flow-control allowance back twice. That pushes the connection's send window past its 31-bit maximum, and a later unsigned check then lets it grow without limit. Wiz says it demonstrated the bug over HTTPS on 64-bit systems serving ordinary static content, with no backend app or third-party modules involved.
The "2Root" part comes from a separate, still-unpatched Linux kernel SCTP bug, dating to kernel 4.15, which Xint says it found. Chained with an nginx bug, it gave root on the host, including from inside a Docker container. Xint is holding back most of the details until a kernel fix exists.
According to Atlas's breakdown of the release, the same update fixes five more bugs, including CVE-2026-118899, a TLS 1.3 request-body infinite loop that can stall a worker and has no workaround.
How close is real-world exploitation?
- In the wild: none confirmed as of November 18, according to Qualys and Wiz.
- Exploit code: Xint posted demo videos showing the chain against AWS, GCP, Azure and bare metal, but left out the final steps. Wiz built lab exploits and says it won't release them. Qualys says some public exploit code does exist but is awkward to use. It needs a direct connection to nginx, minutes of HTTP/2 control frames on one connection, and a specific glibc routine on x86-64.
- Difficulty: Wiz says reliable attacks need memory disclosure and heap grooming tuned to each build. It expects attackers to go after common packaged builds first. Qualys warns that these hurdles won't stop a capable attacker aiming at a specific server.
What to do
1. Upgrade. Move to nginx 1.30.7 or 1.31.9. If you're on an older branch (1.29.x or earlier), no fixed build exists for it, so move to one of those two or to a vendor package that includes the fix. Atlas notes that 1.31.9 also starts rejecting some malformed headers and chunked bodies, which makes 1.30.7 the safer choice if you're worried about compatibility. For NGINX Plus, Qualys and Atlas list 37.3.0.1 and 37.0.8.1 as fixed. R33–R36 have no listed fix.
2. Restart; don't just reload. Qualys and Xint both point out that a reload keeps the old binary in memory. Restart nginx or do a binary upgrade on the fly, and make sure old workers have exited.
3. Check distro packages by full version. Xint notes that Ubuntu 24.04 ships 1.24.0, Ubuntu 22.04 ships 1.18.0 and Debian 12 ships 1.22.1. Fixes usually get backported without changing the upstream version, so check the package release against your vendor's advisory rather than nginx -v.
4. If you can't patch today, turn off HTTP/2. This covers only CVE-2026-123007 and CVE-2026-123633. Clients drop back to HTTP/1.1, and native gRPC will break, so test first.
# nginx 1.25.1 and later, in each affected server block
http2 off;
# 1.9.5–1.25.0: remove "http2" from listen lines, e.g.
listen 443 ssl; # was: listen 443 ssl http2;
# then fully restart and confirm no old workers remain
sudo systemctl restart nginx
For the other bugs, Xint suggests removing QUIC listeners (http3 off, plus clearing Alt-Svc headers), using fixed upstream groups instead of request-built proxy_pass with mirror, and binding mail listeners to loopback.
5. Block the kernel half of the chain. On hosts that don't use SCTP, Xint suggests stopping the module from loading by adding install sctp /bin/false to a file in /etc/modprobe.d/. This won't unload a module that's already loaded or disable SCTP compiled into the kernel.
6. Rebuild images and templates. Qualys says to update container images, Helm charts, machine images and autoscaling templates too. Otherwise vulnerable builds come back on the next deploy.
7. Watch for signs. Wiz and Xint suggest flagging long-lived HTTP/2 connections that move a lot of data, unexpected worker crashes, and any execve calls from the nginx worker user (for example, through auditd).
What to watch
The next steps to watch are a public end-to-end exploit, CISA adding CVE-2026-123007 to its Known Exploited Vulnerabilities catalog, and a Linux kernel fix for the SCTP bug. Any one of them makes this more urgent. Also expect follow-up advisories from appliance, CDN and Kubernetes ingress vendors that bundle nginx.
Sources
- Xint — NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching xint.io
- Wiz — Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 wiz.io
- Qualys — NGINX2Root: Five nginx Flaws, Led by CVE-2026-123007. How to Find, Mitigate, and Patch Now blog.qualys.com
- Atlas — nginx's November 2026 Security Release: 1.30.7 and 1.31.9 atlasum.net