Two critical, unauthenticated remote-code-execution flaws in NGINX's HTTP/2 code were disclosed on 18 November 2026. According to Wiz, both are fixed in NGINX 1.30.7 stable and 1.31.9 mainline. If you run NGINX as a web server or reverse proxy on a VPS, in Docker or in a homelab, check two things: your version, and whether HTTP/2 is turned on. Both bugs need HTTP/2 enabled to be reachable.
One caveat up front. Everything below comes from Wiz's write-up. Wiz is one of the teams that found the bugs, so it is a primary source on the research, but it is not F5's own advisory. Check F5's advisory or nginx.org before you rely on the exact version numbers.
What Wiz says the two NGINX HTTP/2 bugs do
Wiz's post by Nir Ohfeld and Tomer Schwartz says Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint each found the flaws independently and reported them to F5, the company behind NGINX. Both are rated Critical with a CVSS 4.0 score of 9.2.
- CVE-2026-123633 is a use-after-free in HTTP/2 connection handling. It hits reverse-proxy processing when available connection slots run low. Wiz says it first affects NGINX OSS 1.19.7.
- CVE-2026-123007 is an integer underflow in HTTP/2
send_windowflow-control accounting that leads to an invalid memory copy. Wiz says it first affects 1.9.5, from 2015, and that it demonstrated the bug on plain static-file serving over HTTPS on 64-bit systems, with no backend app or third-party modules.
Two details make this worse than a typical web bug. The flaws are in NGINX itself, so well-written application code behind it doesn't protect you. And Wiz says ASLR doesn't stop either one, because an attacker can get a memory read first.
Fixed versions, per Wiz's table
| Product | CVE | Fixed in |
|---|---|---|
| NGINX OSS | Both | 1.30.7 (stable) or 1.31.9 (mainline) |
| NGINX Plus | CVE-2026-123633 | 37.0.7.1 and 37.2.0.1 |
| NGINX Plus | CVE-2026-123007 | 37.0.8.1 and 37.3.0.1 |
For NGINX Plus, Wiz lists R33 / 37.0.0 as the first affected release for both bugs.
Wiz's post is a little inconsistent on availability. Its summary tells readers to update "when released" and "as soon as available", while its timeline says F5's security release shipped on 18 November. If your distribution or the Docker image you use doesn't offer one of those versions yet, use the stopgap below.
How to check your NGINX version and HTTP/2 setting
Run nginx -v on the server, or inside the container, to print the version. Anything below the fixed releases in the table should be treated as affected.
To see whether HTTP/2 is on, dump the full loaded config and search it:
nginx -T | grep -n http2
Look for http2 on; in a server block, or http2 as a parameter on a listen line, such as listen 443 ssl http2;.
The http2 off; stopgap if you can't upgrade yet
Wiz's recommended workaround is to turn HTTP/2 off until you can patch:
- In each affected server block, set
http2 off;. This directive works on NGINX 1.25.1 or later. - Remove the
http2parameter from anylistendirectives. On versions older than 1.25.1, this is the way to disable it. - Run
nginx -tto check the config for syntax errors. Before reloading, note the current worker process IDs withps aux | grep 'nginx: worker'. Then reload withnginx -s reload(orsudo systemctl reload nginxon a systemd host) and test that your applications still work. - Run
ps aux | grep 'nginx: worker'again. The worker process IDs you noted before the reload should be gone, replaced by new ones. If an old ID is still listed, it is still finishing requests under the old config; wait and check again. - Turn HTTP/2 back on after you upgrade.
Signs to watch in your logs
Wiz suggests watching for unexpected NGINX worker crashes or commands launched by the NGINX process. It labels these as general warning signs, not confirmed indicators of these two flaws.
What to watch next
The thing to check is when your package source ships 1.30.7 or 1.31.9: your distribution's NGINX package or the official Docker image. Until it does, keep HTTP/2 off on any server reachable from the internet.