nginx2root (CVE-2026-123007): Check and Patch Your nginx Server Today
On November 18, the nginx team shipped two new versions of the world's busiest web server with ten security fixes inside. Five of them carry a scary nickname, nginx2root, and the worst one, CVE-2026-123007, has been hiding in nginx's HTTP/2 code for more than ten years.
Here's why it matters. On an unpatched server with HTTP/2 switched on, an attacker with no account and no password can send a stream of crafted requests and run commands as the nginx worker process. That's the program serving your website.
The fix is quick, and most servers can be checked in five minutes. This guide shows you how to tell whether you're affected (the version number can mislead you), how to patch, and what to switch off if you can't update today.
Last checked: November 20, 2026.
The short version
| What it is | An integer overflow in nginx's HTTP/2 flow control that corrupts memory and can lead to remote code execution |
| Affected | nginx 1.9.5 to 1.31.8, when HTTP/2 is on. NGINX Plus R34 to R36 and 37.x before the fixed builds |
| Fixed in | nginx 1.30.7 (stable) and 1.31.9 (mainline), NGINX Plus 37.0.8.1 and 37.3.0.1, plus distro updates from Ubuntu, Debian and others |
| Severity | F5 rates it 9.2 out of 10 (CVSS v4) |
| Attacked yet? | No attacks reported as of November 19, but a public proof of concept exists |
| Quick workaround | Turn HTTP/2 off until you can update |
What is nginx2root, in plain English?
Think of HTTP/2 as a highway with many lanes. To stop one lane from flooding the server, both sides keep a running "window" of how much data each lane may still send. A browser can raise that window by sending a small message called WINDOW_UPDATE.
nginx checked those updates, but it forgot to count data that was already queued. A careful attacker can push the counter past its limit so it wraps around. nginx then trusts a number that's wrong, and reads and writes memory it shouldn't touch. That's the doorway to running code.
The flaw was found by the security firm Xint. It reported it to F5, the company behind nginx, on October 16. Xint's automated scanner then found four more bugs that each lead to code execution on their own, in different parts of nginx. Together they make up nginx2root:
| CVE | Where the bug lives | You're exposed only if you use… | Vulnerable versions |
|---|---|---|---|
| CVE-2026-123007 | HTTP/2 flow control | HTTP/2 | 1.9.5 to 1.31.8 |
| CVE-2026-123633 | HTTP/2 connection handling | HTTP/2 with requests passed to a backend | 1.19.7 to 1.31.8 |
| CVE-2026-123634 | DNS resolver | the resolver directive with subrequests such as mirror |
0.6.18 to 1.31.8 |
| CVE-2026-121810 | HTTP/3 (QUIC) | HTTP/3 with requests passed to a backend | 1.25.0 to 1.31.8 |
| CVE-2026-113425 | Mail proxy | nginx as an IMAP, POP3 or SMTP proxy | 0.5.33 to 1.31.8 |
The same release also fixes five lesser bugs. They include an endless loop that can freeze a worker on any HTTPS site (CVE-2026-118899) and a buffer overflow when try_files is used with alias (CVE-2026-125283). One update covers all ten.
Am I affected? Check the right way
Start with the version:
nginx -v
If it prints 1.30.7, 1.31.9 or newer, you're on a fixed release. If it prints something older, don't panic yet.
Linux distributions rarely jump to a new nginx version in the middle of a release. They copy the fix into the version they already ship. This is called backporting: the number stays the same and only the package revision changes. So nginx -v on a fully patched Ubuntu 24.04 still says 1.24.0.
The real question is whether your installed package contains the fix. On Ubuntu and Debian, search the changelog that came with it:
zcat /usr/share/doc/nginx-common/changelog.Debian.gz | grep -m1 CVE-2026-123007
If that prints a line, you're patched. If it prints nothing, you aren't yet.
We checked Ubuntu's own changelog for 24.04 on November 20. The fixed package is 1.24.0-2ubuntu7.20, dated November 18. It patches CVE-2026-123007 and four others from this batch. Canonical's note for the HTTP/2 fix reads "Arbitrary code execution in send_window".
Fixed packages for the most common systems:
| System | Fixed package |
|---|---|
| Ubuntu 26.04 LTS | 1.28.3-2ubuntu1.13 |
| Ubuntu 24.04 LTS | 1.24.0-2ubuntu7.20 |
| Ubuntu 22.04 LTS | 1.18.0-6ubuntu14.23 |
| Ubuntu 20.04 and older | through Ubuntu Pro (ESM) |
| Debian 13 (trixie) | 1.26.3-3+deb13u11 |
| Debian 12 (bookworm) | 1.22.1-9+deb12u11 |
On Red Hat, AlmaLinux and Rocky Linux, use:
rpm -q --changelog nginx | grep -m1 CVE-2026-123007
Step 1: See which risky features you use
Each bug needs a certain feature to be switched on. This prints your whole live configuration and picks out the lines that matter:
sudo nginx -T 2>/dev/null | grep -nE "http2|quic|http3|resolver|mirror|^\s*mail\s*\{"
http2 on;orlisten 443 ssl http2;means HTTP/2 is on. That's the big one, and most HTTPS sites have it.quicorhttp3means HTTP/3 is on.resolverandmirrorlines point to the DNS bug.- A
mail {block means you run the mail proxy.
No matches doesn't mean you can skip the update. The endless-loop bug affects any HTTPS site. Patch anyway; this check tells you how urgent it is.
Step 2: Install the fix
Ubuntu and Debian:
sudo apt update
sudo apt install --only-upgrade nginx nginx-common
sudo systemctl restart nginx
Red Hat, AlmaLinux, Rocky Linux: run sudo dnf update nginx, then sudo systemctl restart nginx. Confirm with the rpm check above. If your vendor hasn't shipped the update yet, use the workarounds below in the meantime.
Using the nginx.org repository or building from source: move to 1.30.7 (stable) or 1.31.9 (mainline).
Docker: pull nginx:1.30.7 or nginx:1.31.9 (both are on Docker Hub) and redeploy. Restarting an old container changes nothing, because the fix only arrives with the new image.
NGINX Plus: move to 37.0.8.1 or 37.3.0.1. F5 lists no fix for R34 to R36, so those need an upgrade to 37.x.
Restart, don't just reload. A reload starts new workers, but old ones can stay alive to finish open connections, and they still run the old code. Xint advises a full restart after patching.
Can't update today? Switch off what's vulnerable
These are stopgaps. Remove them once you've updated.
HTTP/2 (covers CVE-2026-123007 and CVE-2026-123633). On nginx 1.25.1 or newer, put this in the http block and remove any http2 on; lines from your server blocks:
http2 off;
On older versions, delete the word http2 from your listen lines, so listen 443 ssl http2; becomes listen 443 ssl;. Then run sudo nginx -t and restart.
Browsers quietly fall back to HTTP/1.1, so your site keeps working. The one thing that breaks is gRPC, which needs HTTP/2.
HTTP/3: remove quic from the listen lines, set http3 off;, and tell browsers to forget it with add_header Alt-Svc 'clear';.
DNS resolver: use fixed upstream blocks instead of names looked up per request, and turn off mirror where you don't need it. Xint warns that other subrequest features such as SSI can reach the same bug, so this one really wants the patch.
Mail proxy: bind the IMAP, POP3 and SMTP listeners to 127.0.0.1 or block them at the firewall.
Why "root"? The Linux kernel part
On its own, the nginx bug gives an attacker the rights of the nginx worker, usually a low-power user like www-data. The "root" in the name comes from a second bug that Xint found in the Linux kernel's SCTP code, a networking protocol most web servers never use. Chained together, the two gave Xint full root control of the machine, even from inside a Docker container.
There was no kernel patch when this guide was written. If you don't use SCTP (almost no web server does), you can stop the module from loading:
echo "install sctp /bin/false" | sudo tee /etc/modprobe.d/disable-sctp.conf
lsmod | grep sctp
If lsmod prints nothing, SCTP isn't loaded. If it prints a line, the module is already in memory and a reboot clears it. This blocks future loading only; it can't remove SCTP if your kernel has it built in.
How worried should you be?
Serious, but not panic. The facts so far:
- A public exploit exists. Rapid7 published an analysis and proof of concept on November 18. Tenable reports that Rapid7 calls the exploit "constrained", so it doesn't work everywhere.
- No attacks seen yet. Tenable found no reports of exploitation in the wild, and the bugs weren't on CISA's list of known exploited vulnerabilities as of November 19.
- The target pool is huge. Censys counted, as cited by Tenable, about nine million internet-facing nginx services on an affected version with HTTP/2 on, though some of those already carry distro backports.
Public code plus millions of targets usually means scanning starts within days. The OpenSSH SSHole bug showed how fast that window closes. Patch this week, ideally today.
Make the next patch automatic
Servers that install security updates on their own picked up Ubuntu's fix within a day of it landing on November 18. On Ubuntu and Debian it takes a minute:
sudo apt install unattended-upgrades
sudo dpkg-reconfigure -plow unattended-upgrades
Our 30-minute Linux VPS security checklist sets this up along with SSH keys, a firewall and Fail2ban. While you're at it, make sure your HTTPS certificate isn't close to expiring with our free SSL certificate checker.
Quick answers
What is CVE-2026-123007?
An integer overflow in nginx's HTTP/2 flow-control code. Crafted WINDOW_UPDATE messages can corrupt memory and let an unauthenticated attacker run code as the nginx worker. It's the lead bug of the nginx2root set.
Which nginx versions are affected? Every release from 1.9.5 (2015) through 1.31.8, when HTTP/2 is enabled. The other four nginx2root bugs reach back as far as 0.5.33, depending on the feature.
What version fixes nginx2root? nginx 1.30.7 (stable) or 1.31.9 (mainline), both released November 18, 2026. On Ubuntu and Debian, install your distro's security update instead; it keeps the old version number.
My Ubuntu 24.04 server says nginx 1.24.0. Am I vulnerable?
Not if the package is 1.24.0-2ubuntu7.20 or later. Check with zcat /usr/share/doc/nginx-common/changelog.Debian.gz | grep CVE-2026-123007.
Does turning off HTTP/2 break my site? No. Browsers fall back to HTTP/1.1 on their own. Only gRPC services need HTTP/2.
Does Cloudflare or a CDN protect me? Partly. Visitors talk HTTP/2 to the CDN, which usually reaches your server over HTTP/1.1. But if attackers can find your server's real IP address, they can skip the CDN entirely. Patch either way.
Is Apache affected? No. Apache had its own, separate HTTP/2 bug a week earlier, covered in our Apache CVE-2026-119618 guide.
I'm on shared hosting. What should I do? Your host manages nginx, so there's nothing to install. If you want to be sure, ask support whether CVE-2026-123007 has been patched.
One command to check, one to update, one restart. If you look after a server running nginx, do it before the people reading this patch get there first.
Sources
The facts in this article were checked against these sources.
- nginx: security advisories nginx.org
- nginx: Changes with nginx 1.31.9 (18 Nov 2026) nginx.org
- F5: K000163926, CVE-2026-123007 my.f5.com
- Xint: nginx2root, remote code execution in nginx xint.io
- Tenable: nginx2root FAQ tenable.com
- Ubuntu: CVE-2026-123007 ubuntu.com
- Debian security tracker: CVE-2026-123007 security-tracker.debian.org