Two memory-safety bugs in NGINX's HTTP/2 code. CVE-2026-123007 is real but expensive: about 128 GB on a single connection to run code. The most exposed are community ingress-nginx clusters, with HTTP/2 on by default and no patch ever coming.
nginx -v. Config: nginx -T | grep http2.Both are memory-safety bugs in HTTP/2 handling, each fixed in a few lines. Both are rated CVSS 4.0 9.2, but they are not equally reachable.
A cancelled stream refunds bytes to the send window without checking the HTTP/2 maximum. The bounds check wraps, the window goes negative, and a copy in the TLS send path writes out of bounds.
A connection with a half-received HEADERS frame stays marked "reusable". If its request opens an upstream connection while slots are low, NGINX can free the connection it's still using. nginx.org rates it medium.
*_pass directive or a resolverworker_connections (~960 of 1,024)2³² WINDOW_UPDATE frames of 13 bytes each, plus NGINX's flood-check overhead. That much traffic on one connection is also the best way to spot the attack. musl (Alpine) and ARM64 builds haven't been tested by anyone yet.
A new binary needs a restart (or a USR2 binary upgrade). A config reload keeps the old code running.
1.9.5 – 1.30.6
1.31.0 – 1.31.81.30.7 · 1.31.9Fix outR33+ and 37.0.0+123007: 37.0.8.1 · 37.3.0.1
123633: 37.0.7.1 · 37.2.0.1R33–R36: no fixbefore 5.8.0, 2026-lts-r115.8.0Fix out · HTTP/2 off by defaultbefore 2.9.02.9.0Fix out · HTTP/2 on by defaultevery release (NGINX 1.27.1)—Archived · no fixDebian, Ubuntu, RHEL, Amazon Linux, SUSE, Alpine, Fedora, BitnamiNo fixed tag or package yetWaitingnginx -v will lie. Distro fixes arrive as backports, so the version string stays old. Compare the full package release against your distro's advisory. Forks (OpenResty, Tengine, Angie, freenginx) still carry the unpatched code.HTTP/2 is off unless you turn it on. The module ships in the official image, Alpine and Ubuntu packages, but no default config enables it. What sits in front matters:
Researchers chained CVE-2026-123007 with a still-unpatched Linux SCTP kernel bug (present since Linux 4.15). From an NGINX worker in a Docker container, they reached root on the host of an AWS server, over its public IP.
~128 GB of HTTP/2 frames over one TLS connection. Nothing in access logs.
Runs as the NGINX worker inside the container.
Reachable wherever the container can open an SCTP socket.
Container escape to the node, and from there the cluster.
use-http2: true).use-http2: "false" in the controller ConfigMap, then migrate.install sctp /bin/false in a file under /etc/modprobe.d/.1.30.7, 1.31.9, Ingress Controller 5.8.0, Gateway Fabric 2.9.0 or fixed Plus. Restart, don't just reload.
Blocks both bugs. A reload is enough.
http2 off;
# and drop http2 from listenNo patch will come. Disable HTTP/2, then migrate.
use-http2: "false"Limit inbound bytes per connection. A weaker extra layer, since the attack needs ~60–128 GB.
Removes the kernel step of the container escape.
install sctp /bin/falsegrpc_pass needs it, and those frontends have an upstream, so they're in scope for CVE-2026-123633 too. Patch them first.Don't rely on keepalive_time. HTTP/2 only checks it when a new stream starts, so it won't cut a long attack connection. On versions before 1.25.1, only removing http2 from listen works.The trigger frames are never logged as requests. These are the signals that work, in the order an attack produces them. No team watching around the clock? Upwind MDR →
CVE-2026-123007 being exploited. The cost of the attack is its biggest tell.
What CVE-2026-123633 needs.
worker_connections are not enough, reusing connections
A failed exploit, or the 60 GB denial of service.
worker process ... exited on signal 11 (or 6)
Specific to the public PoC, but a strong signal when you see it.
The clearest sign the attack worked. Upwind runtime detection flags it with full process lineage.
www-data sh -c id; uname -a; cat /etc/passwdSee Upwind cloud detection & response →
HTTP/2 support ships, and with it the CVE-2026-123007 bug.
CVE-2026-123633 is introduced.
F5 publishes fixes (1.30.7 / 1.31.9). Rapid7 releases a public crash trigger and RCE chain for CVE-2026-123007.
We'll update this page as Docker tags and distro packages ship, and if exploitation is seen in the wild.
Upwind inventories images, packages and Kubernetes workloads, maps which NGINX is reachable from the internet, and flags a worker that crashes repeatedly or spawns a shell.