The nginx team shipped nginx 1.30.7 stable and 1.31.9 mainline on November 18, 2026. The pair fixes ten CVEs. Two of them live in the HTTP/2 module, and five research groups found them on their own: Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint.
nginx.org rates the HTTP/2 flow control bug as major and the HTTP/2 use-after-free as medium. Wiz scores both at CVSS 4.0 9.2 and says it confirmed unauthenticated code execution for each. The oldest one, CVE-2026-123007, goes back to nginx 1.9.5 from 2015.
- CVEs fixed in 1.31.9
- 10
- oldest version hit by CVE-2026-123007
- 1.9.5
- Wiz CVSS 4.0 score for both HTTP/2 bugs
- 9.2
The two HTTP/2 bugs
CVE-2026-123007, flow control window overflow. The changelog says an attacker can cause a segmentation fault in a worker process, "or might have potential other impact." Wiz fills in the rest. A client cancels a stream while response data still sits in the queue, and nginx refunds the unsent bytes to h2c->send_window with no check against the HTTP/2 maximum. If the client raised the window in the meantime, the counter lands above the limit. The later bounds check in ngx_http_v2_state_window_update() subtracts the window from the maximum using unsigned math, wraps around, and lets the window grow further. Wiz demonstrated code execution against nginx serving static files over HTTPS on 64-bit systems, with no backend and no third-party modules. Xint reported it to nginx.
CVE-2026-123633, use-after-free. This one needs nginx acting as a proxy with worker_connections running low. A client sends half a HEADERS frame, nginx marks the idle connection as reusable, and then forgets to unmark it once the rest of the frame creates a stream. Later nginx opens an upstream connection, and if it runs short of slots, ngx_drain_connections() can pick that same HTTP/2 connection, free it, and hand control back to the request still using its memory. Albert of Vexera AI gets the credit in the changelog.
The other eight
| CVE | Issue | nginx.org severity | Vulnerable |
|---|---|---|---|
| CVE-2026-118899 | Infinite loop reading a request body over TLS 1.3 | major | 1.13.0 to 1.31.8 |
| CVE-2026-113425 | Use-after-free in the mail proxy | major | 0.5.33 to 1.31.8 |
| CVE-2026-123634 | Use-after-free in the resolver | medium | 0.6.18 to 1.31.8 |
| CVE-2026-121810 | Use-after-free in HTTP/3 | medium | 1.25.0 to 1.31.8 |
| CVE-2026-120967 | SNI bypass in stream client certificate checks | medium | 1.25.5 to 1.31.8 |
| CVE-2026-125283 | Buffer overflow with alias plus try_files | minor | 0.9.6 to 1.31.8 |
| CVE-2026-123640 | Lax ClientHello parsing in ssl_preread | minor | 1.15.2 to 1.31.8 |
| CVE-2026-120993 | NULL dereference with PROXY protocol v2 | minor | 1.31.4 to 1.31.8 |
Wiz rates the resolver, HTTP/3 and mail proxy bugs at 9.2 as well, each under a specific configuration: an attacker who controls an upstream host name, HTTP/3 in front of a proxied backend, or auth_http in the mail proxy.
1.31.9 also changes behavior. nginx now rejects header lines without a colon, and rejects chunked request bodies that carry too much framing overhead. If you front a client that sends malformed headers, test before you roll out.
Patch, or turn HTTP/2 off until you can
The fixed versions are 1.30.7 on the stable branch and 1.31.9 on mainline. For NGINX Plus, Wiz lists 37.0.7.1 and 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 and 37.3.0.1 for CVE-2026-123007.
If you can't upgrade today, Wiz recommends turning HTTP/2 off on affected servers. On nginx 1.25.1 or later that takes two edits per server block:
server {
- listen 443 ssl http2;
- http2 on;
+ listen 443 ssl;
+ http2 off;
server_name example.com;
}
Then check and reload:
nginx -V 2>&1 | head -1 # confirm the running version
nginx -t && nginx -s reload # apply the HTTP/2 change
ps -o pid,lstart,cmd -C nginx # old workers should be gone
Turn HTTP/2 back on after the upgrade.
Wiz advises watching for unexpected worker crashes and for commands that nginx processes spawn. It calls both general warning signs, with no confirmed indicators for these bugs.
This week
- Inventory every nginx you run, including the ones baked into container images and ingress controllers, and find the ones with HTTP/2 on.
- Upgrade to 1.30.7 or 1.31.9. Check the version string on each host after you pull the new package or image.
- On servers you can't upgrade yet, set
http2 off;, drophttp2fromlisten, and reload. - If you proxy with HTTP/3, run the resolver against hosts you don't control, or use the mail proxy, put those servers first in the queue.
Volodymyr Chornous

