Two HTTP/2 bugs lead the release, but the same patch closes four web-facing remote code execution flaws, each tied to a different config. In Kubernetes, the blast radius reaches past the ingress pod.
nginx -v. Config check: nginx -T.Each one gives an unauthenticated attacker code execution as the NGINX worker. Which ones reach you depends on what your config turns on.
An accounting error turns into an out-of-bounds memory copy. Works even on a static-file-only server.
When connection slots run low, NGINX can close a client's connection while its own request still uses it.
Hit when NGINX resolves upstream names per request and a subrequest feature is in play.
proxy_pass + mirror or SSIF5 rates the impact as a worker restart. Researchers demonstrated code execution.
A config reload doesn't replace the running binary. Upgrade, then restart (or do a binary upgrade with USR2).
1.30.0 – 1.30.61.30.7Fix out1.31.0 – 1.31.81.31.9Fix outR34 – R36, 37.x37.0.8.1 · 37.3.0.1R34–R36: no fixall, archived at v1.15.1—No fix comingUbuntu 22.04 · 1.18.0
Ubuntu 24.04 · 1.24.0
Debian 12 · 1.22.1Backports, per distro advisoryCheck packagenginx -v can lie. Distros backport fixes without changing the version string, so 1.24.0 may be patched or not. Compare the full package release against your distro's advisory. Images built on NGINX stay vulnerable until rebuilt and redeployed.Sources: nginx.org advisories · Upwind analysis · Wiz
The ingress pod shares a kernel with the node. Researchers ("nginx2root") chained CVE-2026-123007 with an unpatched Linux SCTP use-after-free to escape the container.
Crafted HTTP/2 frames over TLS. Nothing shows in access logs.
Runs as the NGINX worker inside the ingress container.
Opening an SCTP socket auto-loads the vulnerable module on many distros.
Container escape to the node, and from there the cluster.
use-http2: "false" in the controller ConfigMap, then plan a migration.install sctp /bin/false in /etc/modprobe.d/.Covers 123007 and 123633. On 1.25.1+:
http2 off;
# and drop http2 from listenCovers 121810. Remove QUIC listeners:
http3 off;Covers 123634. Point proxy_pass at a fixed upstream group, not a variable.
Old workers keep existing HTTP/2 sessions alive after a reload. Confirm h2 is gone:
openssl s_client -alpn h2grpc_pass) break with HTTP/2 off. Test before rolling it out, and patch those hosts first.The trigger frames are hidden by TLS and never logged as requests. Watch behavior instead. Signals 2–4 have innocent causes alone; together, or followed by signal 1, they justify blocking and investigating. No team watching around the clock? Upwind MDR →
A worker has no reason to spawn a shell, curl or id. Upwind runtime detection flags this with full process lineage.
www-data sh -c id; uname -a; cat /etc/passwdSee Upwind cloud detection & response →
Failed attempts crash workers before one succeeds. Look in the master error log and for core dumps.
worker process 4127 exited on signal 11
A single long-lived TLS connection receiving tens of GB and sending little, plus many short TLS connections from the same source.
A web-server container opening SCTP sockets is the kernel-escape step of the nginx2root chain.
Reported to F5: the HTTP/2 use-after-free (CVE-2026-123633).
F5 shares a patch with researchers for review.
Second bug reported: the flow-control underflow (CVE-2026-123007).
F5 security release and public disclosure. NGINX 1.30.7 / 1.31.9.
We'll update this page as distros ship backports and as exploitation is seen in the wild.
Upwind inventories images, packages and Kubernetes workloads, maps which ingress is reachable from the internet, and flags an NGINX worker spawning a shell at runtime.