Patch out F5 shipped fixes on Nov 18: NGINX 1.30.7 stable · 1.31.9 mainline. Community ingress-nginx will not be fixed. Check your version →
Unauthenticated RCE ● Patch available ingress-nginx: no fix coming

NGINX.
Four RCEs. One patch.

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.

9.2CVSS 4.0, unauthenticated
4web-facing RCEs, one release
2015bug present since 1.9.5
CVE-2026-123007 · CVE-2026-123633 · CVE-2026-123634 · CVE-2026-121810 · Updated Nov 18, 2026 · Upwind Research & MDR

Am I exposed?

Tell us what you run. We'll tell you which of the four apply.
Run nginx -v. Config check: nginx -T.
What F5 fixed

Four bugs, four configs

Each one gives an unauthenticated attacker code execution as the NGINX worker. Which ones reach you depends on what your config turns on.

01
CVE-2026-123007

HTTP/2 flow-control underflow

An accounting error turns into an out-of-bounds memory copy. Works even on a static-file-only server.

Needs: HTTP/2 · affected since 1.9.5
02
CVE-2026-123633

HTTP/2 connection use-after-free

When connection slots run low, NGINX can close a client's connection while its own request still uses it.

Needs: HTTP/2 + proxying · since 1.19.7
03
CVE-2026-123634

Request-time DNS use-after-free

Hit when NGINX resolves upstream names per request and a subrequest feature is in play.

Needs: resolver + variable proxy_pass + mirror or SSI
04
CVE-2026-121810

HTTP/3 proxy bug

F5 rates the impact as a worker restart. Researchers demonstrated code execution.

Needs: HTTP/3 + proxying
Fixed versions

Patch, then restart

A config reload doesn't replace the running binary. Upgrade, then restart (or do a binary upgrade with USR2).

ProductVulnerableFixed inStatus
NGINX OSS stable1.30.0 – 1.30.61.30.7Fix out
NGINX OSS mainline1.31.0 – 1.31.81.31.9Fix out
NGINX PlusR34 – R36, 37.x37.0.8.1 · 37.3.0.1R34–R36: no fix
ingress-nginx (community)all, archived at v1.15.1—No fix coming
Distro packagesUbuntu 22.04 · 1.18.0
Ubuntu 24.04 · 1.24.0
Debian 12 · 1.22.1
Backports, per distro advisoryCheck package
⚠️
nginx -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.
Find every image running a vulnerable NGINX package →

Sources: nginx.org advisories · Upwind analysis · Wiz

Why Kubernetes is worse

From one HTTP/2 stream to node root

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.

1

Internet → ingress

Crafted HTTP/2 frames over TLS. Nothing shows in access logs.

2

Code exec in worker

Runs as the NGINX worker inside the ingress container.

3

SCTP kernel bug

Opening an SCTP socket auto-loads the vulnerable module on many distros.

4

Host root

Container escape to the node, and from there the cluster.

Community ingress-nginx

  • HTTP/2 is on by default.
  • Archived March 2026 at v1.15.1. These fixes won't ship.
  • Now: set use-http2: "false" in the controller ConfigMap, then plan a migration.
Not its first time: IngressNightmare →

Close the kernel step

  • The SCTP bug (since Linux 4.15) has no patch yet.
  • Block the module where unused: install sctp /bin/false in /etc/modprobe.d/.
  • This doesn't unload a module that's already loaded.
How Upwind spots container escapes →
Can't patch today?

Stopgaps that work

01

Turn off HTTP/2

Covers 123007 and 123633. On 1.25.1+:

http2 off; # and drop http2 from listen
02

Turn off HTTP/3

Covers 121810. Remove QUIC listeners:

http3 off;
03

Fix the upstream

Covers 123634. Point proxy_pass at a fixed upstream group, not a variable.

04

Verify

Old workers keep existing HTTP/2 sessions alive after a reload. Confirm h2 is gone:

openssl s_client -alpn h2
⚠️ gRPC needs HTTP/2Native gRPC frontends (grpc_pass) break with HTTP/2 off. Test before rolling it out, and patch those hosts first.
Detect attempts

What exploitation looks like

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 →

Strongest

1 · NGINX worker starts a program

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/passwd
See Upwind cloud detection & response →
Supporting

2 · Repeated worker crashes

Failed attempts crash workers before one succeeds. Look in the master error log and for core dumps.

worker process 4127 exited on signal 11
Supporting

3 · One huge, one-sided connection

A single long-lived TLS connection receiving tens of GB and sending little, plus many short TLS connections from the same source.

Supporting

4 · SCTP from a web container

A web-server container opening SCTP sockets is the kernel-escape step of the nginx2root chain.

Timeline

How it unfolded

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.

Related research

More from Upwind

Upwind customers

Find exposed NGINX in minutes

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.