A flaw in nginx, the open-source web server that sits in front of a huge share of the world’s websites, can let an attacker with no password run code on a vulnerable server. The bug, CVE-2026-123007, lives in how nginx handles HTTP/2 flow control, and it reaches back to version 1.9.5. The fix shipped on November 18 in nginx 1.31.9 mainline and 1.30.7 stable.
Security firm Rapid7, whose researcher Stephen Fewer found the bug, rates it 9.2 out of 10 on the CVSS v4 scale, which is critical. The nginx project’s own advisory page lists the issue as “Memory corruption in HTTP/2 flow control” with major severity and marks every release from 1.9.5 through 1.31.8 as vulnerable.
What the nginx bug does
HTTP/2 lets one connection carry many requests at once. To stop a server from flooding a slow client, the client hands out “credit,” a running allowance of how many bytes the server may send. nginx keeps one credit counter per stream and one for the whole connection.
According to Rapid7’s write-up, an attacker can make nginx return too much credit when queued response data is cancelled, pushing the connection counter past the maximum the protocol allows. The next credit check then underflows: an unsigned subtraction wraps around into an enormous number. After enough further credit frames, nginx ends up treating a giant value as a negative response length, builds a broken memory buffer and copies data outside its bounds. With the right memory layout, that can leak addresses and overwrite a callback, letting an attacker run commands with the permissions of the nginx worker process.
Rapid7 says it built a working proof of concept against a Docker image of nginx 1.31.8 with HTTP/2 and TLS switched on. It has not shown that code can run as root or as the nginx master process.
Why it is hard to pull off
The catch is bandwidth. The attack needs about 128 GB of HTTP/2 traffic, and nginx closes connections after one hour by default. Rapid7’s exploit also depends on a particular optimized memory-copy routine in glibc that is picked on x86-64 processors with AVX-512 support. A proxy sitting between the attacker and nginx would probably not pass the precise frames along.
Running the numbers shows why connection speed matters. 128 GB is about 1,024 gigabits. At 10 Gbit/s that takes roughly 102 seconds, a bit under two minutes. At 1 Gbit/s it takes about 1,024 seconds, or 17 minutes. At 300 Mbit/s it stretches to about 57 minutes, right against the one-hour limit, which is why Rapid7 says slower links cannot succeed.
Which versions to install
The fixed and affected releases, from the nginx advisory and Rapid7’s table:
- nginx Open Source 1.31.0 to 1.31.8: upgrade to 1.31.9.
- nginx Open Source 1.9.5 to 1.30.6: upgrade to 1.30.7.
- NGINX Plus 37.1.0 to 37.2.0.1: upgrade to 37.3.0.1.
- NGINX Plus 37.0.0 to 37.0.7.1: upgrade to 37.0.8.1.
- NGINX Plus R34 to R36: no fixed release listed.
The same release also closes nine other holes, including a second HTTP/2 use-after-free (CVE-2026-123633), a use-after-free in the DNS resolver, a use-after-free in HTTP/3, an infinite loop when reading request bodies over TLS 1.3 and an SNI bypass in stream client-certificate checks. Anyone who cannot patch right away can cut exposure by turning HTTP/2 off, though that trades away its speed benefits.
How it was disclosed
Rapid7 contacted F5, which owns nginx, on November 11. F5 confirmed the bug and assigned a CVE on November 16, and both companies went public on November 18. Bugs in core internet software keep turning up in large batches this year, much like the AI-assisted fixes Linus Torvalds described in our story on the Linux 7.4 merge window, and the push to prove code correct covered in DeepMind’s verification of Signal’s encryption code. More security coverage sits on our Tech page.
The nginx advisory page now lists 10 new CVEs dated to this release, the largest single batch for the server this year.
Image: Carl Lender, CC BY 2.0 via Wikimedia Commons
This article was produced with AI assistance and reviewed by our Editorial Desk. How we work.



