NGINX HTTP/2 RCE: how CVE-2026-123633 and CVE-2026-123007 expose servers, and how to check yours
NGINX HTTP/2 RCE CVE-2026-123633 and CVE-2026-123007: fixed in 1.30.7 and 1.31.9, Ubuntu USN-9159-1 and Debian DSA-6642-1 versions, how to check exposure.
The NGINX HTTP/2 RCE flaws CVE-2026-123633 and CVE-2026-123007 are two memory-safety bugs in how NGINX handles HTTP/2 connections, and researchers say each can let an unauthenticated attacker run code on the server. F5 fixed them on 18 November 2026 in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), in a release that also patched eight other CVEs.
Wiz rates both at CVSS 4.0 9.2, and Ubuntu and Red Hat classify them as high or critical. At the time of writing I found no report of exploitation in the wild, and neither CVE is in the CISA KEV catalog. Wiz and Xint both built working exploits but have not published them.
What happened
Several teams found the same bugs independently. The nginx.org changelog credits Xint for CVE-2026-123007 and “Albert of Vexera AI” for CVE-2026-123633, and Wiz lists itself, Ikotas Labs, Metnir, Rapid7 and Xint as reporters. Both Wiz and Xint used AI-assisted tooling.
| CVE | Bug | nginx.org severity | Vulnerable OSS versions |
|---|---|---|---|
| CVE-2026-123007 | Memory corruption in HTTP/2 flow control | major | 1.9.5 to 1.31.8 |
| CVE-2026-123633 | Use-after-free in HTTP/2 | medium | 1.19.7 to 1.31.8 |
Note the gap: nginx.org labels CVE-2026-123633 “medium”, while Wiz scores it 9.2. F5’s own description says code execution is possible “on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR”. Wiz says it confirmed RCE with an ASLR bypass.
Other fixes in the same release, per nginx.org:
- CVE-2026-113425 (major): use-after-free in the mail proxy. Xint says the path needs a
mailblock withproxy onandauth_http, and no valid credentials. - CVE-2026-123634 (medium): use-after-free in the resolver when the same name is resolved in parallel subrequests.
- CVE-2026-121810 (medium): use-after-free in HTTP/3 when
worker_connectionsrun low. - CVE-2026-118899 (major): infinite loop while reading a request body over TLS 1.3.
- CVE-2026-125283 (minor): buffer overflow when
try_filesandaliasare combined in certain configurations. - CVE-2026-120967, CVE-2026-120993 and CVE-2026-123640 cover stream SNI client certificate checks, PROXY protocol v2 (mainline 1.31.4 to 1.31.8 only) and
ssl_preread.
The attack chain, step by step
CVE-2026-123633, use-after-free. Based on Wiz’s write-up:
- The attacker sends part of an HTTP/2
HEADERSframe. With no active streams, NGINX marks the connection as reusable (safe to close when it needs room). - The rest of the frame arrives and a request stream starts, but the connection is never taken off the reusable list.
- NGINX opens an upstream connection to proxy the request. If free connection slots are low, it drains reusable connections, and can pick this one.
- If sending
GOAWAYfails, the error path frees the connection while its request is still running. The request code then uses freed memory.
This path needs NGINX acting as a reverse proxy.
CVE-2026-123007, send_window underflow.
- When a stream is cancelled with data still queued, NGINX refunds the unsent amount to the connection’s
send_windowwithout checking the HTTP/2 maximum. - The window-update bounds check subtracts that oversized value from the maximum using unsigned arithmetic, which wraps around and lets the attacker keep raising the window with
WINDOW_UPDATEframes. - The value later becomes a negative length in the send path, which ends in an out-of-bounds memory copy in the TLS code.
Wiz confirmed RCE on official 1.31.7 and 1.31.8 builds over HTTPS on 64-bit systems serving static files, with no backend. Xint chained CVE-2026-123007 with a separate Linux kernel SCTP flaw to get root on the host, including escaping a Docker container.
Why it worked
Old code in a hot path. The flow control bug has been there since HTTP/2 arrived in 1.9.5 in 2015, in software Xint counted on 56.7 million Shodan hosts.
Two pieces of state that had to agree did not. In both bugs, one part of NGINX trusted a value another part had already invalidated: a “reusable” flag on a busy connection, and a window counter past its maximum.
Logs will not show it. Xint notes that the WINDOW_UPDATE and RST_STREAM frames used for CVE-2026-123007 are not logged as requests, and TLS hides them on the wire.
How to check if you are affected
- Version: run
nginx -v. Official builds from 1.9.5 to 1.31.8 are vulnerable to CVE-2026-123007. Fixed: 1.30.7 or 1.31.9 and later. On distro packages the upstream version does not change with backports, so check the full package version (dpkg -l nginxorrpm -q nginx). - HTTP/2 module:
nginx -V 2>&1 | grep -o -- '--with-http_v2_module'. - HTTP/2 enabled:
sudo nginx -T 2>/dev/null | grep -nE 'listen .*http2|http2 on'on the running config, orgrep -rnE 'http2' /etc/nginx/on disk. - External exposure: from outside,
openssl s_client -connect HOST:443 -servername HOST -alpn h2 </dev/null 2>&1 | grep ALPN. “ALPN protocol: h2” means HTTP/2 is reachable. Behind a CDN, also test the origin directly. - Other features:
grep -rnE '^\s*mail\s*\{|auth_http' /etc/nginx/for the mail proxy, andgrep -rnE 'quic|http3 on' /etc/nginx/for HTTP/3. - Distro status (updated 21 November): see “Fixed packages on Ubuntu and Debian” below. Red Hat lists RHEL 8, 9 and 10 nginx as “Affected”, with no fixed package yet (checked 19 November).
Fixed packages on Ubuntu and Debian
Ubuntu USN-9159-1 (19 November) fixes CVE-2026-123007, CVE-2026-123633, CVE-2026-113425, CVE-2026-123634, CVE-2026-118899, CVE-2026-120967, CVE-2026-121810 and CVE-2026-123640 in nginx. Fixed package versions:
| Ubuntu release | nginx fixed version (USN-9159-1) |
|---|---|
| 26.10 | 1.30.4-7ubuntu1.2 |
| 26.04 LTS | 1.28.3-2ubuntu1.13 |
| 24.04 LTS | 1.24.0-2ubuntu7.20 |
| 22.04 LTS | 1.18.0-6ubuntu14.23 |
| 20.04 LTS (Ubuntu Pro) | 1.18.0-0ubuntu1.7+esm5 |
| 18.04 LTS (Ubuntu Pro) | 1.14.0-0ubuntu1.11+esm6 |
| 16.04 LTS (Pro, Legacy Support) | 1.10.3-0ubuntu0.16.04.5+esm11 |
| 14.04 LTS (Pro, Legacy Support) | 1.4.6-1ubuntu3.9+esm10 |
Ubuntu USN-9182-1 (20 November) is a follow-up that adds CVE-2026-125283 (try_files with alias), CVE-2026-123640 and CVE-2026-118899 for older releases, and supersedes those versions: 24.04 LTS 1.24.0-2ubuntu7.21, 22.04 LTS 1.18.0-6ubuntu14.24, 26.04 LTS 1.28.3-2ubuntu1.14, 26.10 1.30.4-7ubuntu1.3, 20.04 LTS (Pro) 1.18.0-0ubuntu1.7+esm6. Install the latest, not only 1.24.0-2ubuntu7.20.
Debian (Security Tracker, 21 November):
- trixie (13):
1.26.3-3+deb13u11, DSA-6642-1 (the earlier1.26.3-3+deb13u10is vulnerable). - bookworm (12):
1.22.1-9+deb12u11, DLA-4918-1. - sid:
1.30.6-4; forky1.30.6-3was still listed vulnerable. - DSA-6642-1 covers CVE-2026-113425, CVE-2026-118899, CVE-2026-120967, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-123640 and CVE-2026-125283. This corrects my 19 November note that Debian bookworm and trixie were still vulnerable.
CVE-2026-126714 is not an nginx bug. People search it next to nginx, but it is a PHP session handler flaw (partially overwritten session files), fixed in PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13. Its Ubuntu and Debian fixed versions are in the PHP CVE-2026-129289 article.
If your distro build is not patched yet, the official nginx.org package repositories already carry 1.30.7 and 1.31.9.
What defenders should do
- Patch, then restart. Xint warns that a reload does not replace the running binary. Restart NGINX or do a live binary upgrade.
- If you cannot patch yet, disable HTTP/2. Wiz, Xint and Red Hat all give the same mitigation:
http2 off;on 1.25.1 and later, and removehttp2fromlistendirectives. It blocks only these two CVEs, and breaks clients that need HTTP/2, such as native gRPC. For the mail proxy, Xint suggests binding listeners to loopback or allow-listing clients; for HTTP/3, removingquiclisteners. - Hunt for signs. Xint suggests watching for long-lived connections with fast-growing
bytes_received, auditingexecveby the worker UID, and greppingerror.logforsignal 11worker exits. Any program started by a worker is the strongest signal.
My take
Wiz explicitly compares this to PHP2Shell, the PHP bug behind the Check Point zero-day chain, where exploitation started a week after the fix. NGINX is a much bigger target, and two teams now hold working exploits. I would not plan on more than days.
If the same hosts run PHP-FPM behind NGINX, the PHP security release with CVE-2026-129289 needs the same package restart, and its fastcgi_keep_conn check applies to your NGINX config. Beyond patching, fix your NGINX inventory: appliances, ingress controllers and container images bundle it, and nginx -v there tells you little. More cases are in exploited vulnerabilities.
Questions for this week: how many of our NGINX instances speak HTTP/2 directly to the internet, which ones are distro builds still waiting on a fix, and would we notice a worker process starting a shell?
Sources
- nginx security advisories · nginx.org, 18 November 2026
- Changes with nginx 1.31.9 · nginx.org, 18 November 2026
- Changes with nginx 1.30.7 · nginx.org, 18 November 2026
- K000163926: NGINX HTTP/2 vulnerability CVE-2026-123007 · F5
- K000163928: NGINX HTTP/2 vulnerability CVE-2026-123633 · F5
- Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 · Wiz Research, 18 November 2026
- NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching · Xint, 18 November 2026
- CVE-2026-123007 · Ubuntu Security, updated 19 November 2026
- CVE-2026-123633 · Ubuntu Security, updated 19 November 2026
- CVE-2026-123007 · Debian Security Tracker
- USN-9159-1: nginx vulnerabilities · Ubuntu Security Notices, 19 November 2026
- USN-9182-1: nginx vulnerabilities · Ubuntu Security Notices, 20 November 2026
- DSA-6642-1 nginx security update · Debian Security Tracker
- CVE-2026-123633 (DLA-4918-1, DSA-6642-1) · Debian Security Tracker
- CVE-2026-123007 · Red Hat Customer Portal