
NGINX HTTP/2 remote code execution (CVE-2026-123007, CVE-2026-123633): what is confirmed and how to check your servers
Two memory-corruption bugs, CVSS 4.0 of 9.2, fixed in NGINX 1.30.7 and 1.31.9. Facts from the researchers and nginx.org, and a checklist.
On November 18, 2026, F5 released NGINX fixes for two memory-corruption bugs in the HTTP/2 code: CVE-2026-123007 and CVE-2026-123633. Several research teams found them independently, and at least two showed remote code execution with ASLR defeated. Both carry a CVSS 4.0 score of 9.2 (Critical) from F5.
Below: what each bug is, who is affected, what the researchers actually showed, and what to do. Every claim links to a primary source; what we could not confirm is marked.
Scores as of 2026-11-19live record →
The two bugs
Both live in ngx_http_v2_module, so a server with HTTP/2 turned off is not exposed to either.
| CVE-2026-123007 | CVE-2026-123633 | |
|---|---|---|
| Bug type | Integer underflow in HTTP/2 flow control (send_window), leading to an out-of-bounds copy in ngx_ssl_send_chain | Use-after-free: an HTTP/2 connection stays on the reusable list, ngx_drain_connections closes it when slots run out, no GOAWAY is sent, and memory is freed while a request is still running |
| Affected (Open Source) | 1.9.5 to 1.31.8 | 1.19.7 to 1.31.8 |
| Needs a reverse proxy? | No. Works on plain static file serving, no backend or third-party modules (Wiz) | Yes. NGINX must open an upstream connection; Xint tested proxy_pass. More likely when worker_connections run short |
| NGINX Plus fixed in | R33 and 37.0.0 affected; fixed in 37.0.8.1 and 37.3.0.1 (Wiz) | R33 and 37.0.0 affected; fixed in 37.0.7.1 and 37.2.0.1 (Wiz) |
| F5 advisory | K000163926 | K000163928 |
| nginx.org severity | major | medium |
The "major" and "medium" labels are nginx.org's own scale, not CVSS. NVD has not scored either entry yet (status Received) and its version ranges are imprecise; take the boundaries from nginx.org and F5.
What was actually shown
- Wiz Research (Nir Ohfeld, Tomer Schwartz) says it reached reliable remote code execution on NGINX serving static files, with ASLR bypassed. Wiz does not publish exploit code (Wiz).
- Xint published a chain it calls "NGINX2root" that goes from remote code execution to root, using one of the two bugs plus an unpatched Linux kernel SCTP flaw. Xint notes that after a worker crashes, the new worker gets the same memory layout, which helps an attacker (Xint).
- Rapid7 (Stephen Fewer) published a proof of concept on GitHub for CVE-2026-123007 that gets code execution on a Docker image of nginx 1.31.8 with HTTP/2 and TLS. Rapid7 says it needs roughly 128 GB of HTTP/2 traffic and that the default one-hour connection limit gets in the way (Rapid7).
- Other teams credited with independent discovery: Metnir and Ikotas Labs.
Timeline
Disclosure (2026, as reported by Wiz and Xint)
- F5 security releaseNGINX Open Source 1.30.7 and 1.31.9, plus NGINX Plus fixes. The same release fixes other CVEs, see below.source
Is it being exploited?
Not as far as anyone has reported. watchTowr's FAQ says no exploitation in the wild had been reported and CISA KEV does not list either CVE. On our side the cards show no KEV entry and no EPSS score yet. Treat that as a snapshot: a public proof of concept exists for CVE-2026-123007, and Rapid7 says the traffic it needs is large, which raises the cost but does not remove the risk for exposed servers.
How to check your servers
- Version: run
nginx -v. Anything below 1.30.7 (stable line) or 1.31.9 (mainline) is affected, if HTTP/2 is on. - HTTP/2: run
nginx -T 2>/dev/null | grep -nE 'http2'and look forlisten ... http2orhttp2 on;. - Reverse proxy:
grep -n proxy_passover the same output tells you whether CVE-2026-123633 is in play. - Distribution packages: distributions backport fixes without changing the upstream version, so
nginx -vmay look old. Compare the full package version with your distribution's advisory. - Containers and appliances: check the image tag or vendor bulletin; many products bundle NGINX.
What to do
- Update to NGINX Open Source 1.30.7 or 1.31.9, or the fixed NGINX Plus release listed above. Restart rather than only reload, so the new binary is the one running.
- If you cannot update now, set
http2 off;in each affectedserverblock (NGINX 1.25.1 or later), or removehttp2from thelistenline, then reload and confirm old worker processes have exited. This closes these two bugs only. gRPC proxying stops working without HTTP/2. - Watch for unusual worker crashes and restarts in the error log; both bugs are memory corruption, and Xint notes that a crashed worker is replaced by one with the same memory layout.
- Do not rely on banner-based "exposed servers" counts; the sources we read say those come from version banners and are not reliable.
Other fixes in the same release
The Nov 18 release fixed more than these two. nginx.org also lists CVE-2026-123634 (use-after-free in the resolver), CVE-2026-121810 (use-after-free in HTTP/3), CVE-2026-113425 (use-after-free in the mail proxy), and CVE-2026-118899, CVE-2026-120993, CVE-2026-125283, CVE-2026-120967 and CVE-2026-123640. Turning HTTP/2 off does not cover those, which is another reason to update rather than only toggle the setting.
Why our card says 8.1 and F5 says 9.2
Our CVE pages for these two currently show CVSS 3.1 with a score of 8.1 (High). F5 gives both: CVSS 3.1 with 8.1 (High) and CVSS 4.0 with 9.2 (Critical). NVD has not published its own score yet. Both are F5's scores, two versions of the scale, not a disagreement about the bug. Use the exposure checks above rather than either number to decide priority.
Do I need to worry if I only serve static files?
Is turning HTTP/2 off enough?
Which versions are safe?
Is there a public exploit?
Data as of 2026-11-19live record →
Sources: nginx.org security advisories, Wiz Research, Xint, NGINX2root, Rapid7. F5 advisories K000163926 and K000163928 are referenced by ID, we could not open the pages.