Wiz Research · 2026-11-18 · major
Nginx HTTP/2 RCE — AI-assisted teams find pre-auth bugs, patch to 1.31.9
In short
Nginx fixed two critical pre-auth HTTP/2 bugs (CVE-2026-123007, CVE-2026-123633) on November 18. Wiz found them with its AI scanning harness, and Xint's automated scan found more. Fixed in 1.31.9 and 1.30.7.
Wiz Research · 2026-11-18 · 4 sources checked

Two pre-auth HTTP/2 bugs in nginx were found with AI help; upgrade to 1.31.9 or 1.30.7, or turn HTTP/2 off.
Key specs
| Cvss 4.0 (wiz) | 9.2 |
|---|---|
| Websites on nginx | 225M+ |
Quick facts
| Main CVEs | CVE-2026-123007, CVE-2026-123633 |
|---|---|
| Affected | nginx 1.9.5 to 1.31.8 (CVE-2026-123007); 1.19.7 to 1.31.8 (CVE-2026-123633) |
| Fixed in | nginx 1.31.9 (mainline) and 1.30.7 (stable) |
| Needs | HTTP/2 enabled; no login |
| Found with | Wiz Atlas AI code scanning; also Xint, Rapid7, Ikotas Labs, Metnir |
| Stopgap | http2 off; in affected server blocks |
What is it?
Nginx 1.31.9 and 1.30.7, released on November 18, 2026, fix a set of memory bugs, and two of them let an attacker run code on a server without logging in. Wiz rates CVE-2026-123007 and CVE-2026-123633 at 9.2 (Critical) under CVSS 4.0. Both only work when HTTP/2 is turned on, which is common on public websites.
How does it work?
CVE-2026-123007 is an integer underflow in HTTP/2 flow control: a refund during stream cancellation pushes the send window past its limit, and a later bounds check wraps into an out-of-bounds memory copy. CVE-2026-123633 is a use-after-free, where a busy HTTP/2 connection stays on the reusable list and gets closed while a request still uses its memory. Wiz says it found both with Wiz Atlas, the harness behind its AI code scanning, and checked the impact with Gemini 4 Carbon and what it calls ChatGPT 5.6 Sol.
Why does it matter?
Wiz says nginx runs more than 225 million websites, so the exposure is huge. Five teams found the same flaws on their own, and Xint says a fully automated scan found four of its five nginx bugs without human guidance. That points to a world where AI makes old, deep bugs in core infrastructure cheap to find, for defenders and attackers alike, and patch windows get shorter.
Who is it for?
anyone running nginx
Frequently asked questions
- How do I protect an nginx server if I cannot upgrade today?
- Wiz advises turning HTTP/2 off until you can upgrade nginx. On nginx 1.25.1 or later, set http2 off; in the affected server blocks and remove the http2 parameter from listen directives. Then test your apps, reload nginx and make sure old worker processes have exited. Turn HTTP/2 back on after moving to 1.31.9 or 1.30.7.
- Which nginx versions fix the HTTP/2 vulnerabilities?
- The nginx.org security advisories list nginx 1.31.9 and later (mainline) and 1.30.7 and later (stable) as not vulnerable. For NGINX Plus, Wiz lists 37.0.8.1 and 37.3.0.1 for CVE-2026-123007, and 37.0.7.1 and 37.2.0.1 for CVE-2026-123633. Linux distribution packages may backport the fixes without changing the version that nginx -v prints.
- What else did Xint find in nginx besides the HTTP/2 bugs?
- Xint's NGINX2Root write-up lists five nginx CVEs: the two HTTP/2 bugs, a resolver use-after-free with mirror (CVE-2026-123634), an HTTP/3 use-after-free (CVE-2026-121810) and a mail proxy use-after-free (CVE-2026-113425). Xint also found a Linux kernel SCTP bug that, chained with an nginx bug, gave root on the host, even from inside a Docker container.
- How did AI help find the nginx bugs?
- Wiz Research says it discovered both HTTP/2 bugs with Wiz Atlas, the harness behind its AI code scanning product, and used Gemini 4 Carbon and ChatGPT 5.6 Sol to confirm their impact. Xint says one of its researchers found CVE-2026-123007 while preparing for ZeroDay Cloud 2026, and a fully automated Xint scan found the other four nginx bugs.
Try it
nginx -v # upgrade if below 1.31.9 (mainline) or 1.30.7 (stable)