Specimen No. 1487 · Habitat H4 · DevOps & IT

Two NGINX HTTP/2 bugs can lead to remote code execution. Update to 1.30.7 or 1.31.9

nginx 1.30.7 and 1.31.9 fix 10 CVEs, two of them HTTP/2 memory bugs Wiz rates 9.2. If you can't patch yet, turn HTTP/2 off. F5 says no exploitation seen.

WILDNESS2 / 5 · MOSTLY TAMED
Verified: nginx.org advisories and release note, Wiz Research and Rapid7 write-ups (18 November), read 19 November.Only claimed: CVSS 9.2 is Wiz's rating. F5 told The Register it has seen no exploitation. We reproduced nothing.
A paper castle gatehouse with parcels lined up through its arch and a rust-red patch being stitched over a crack in its wooden door.
Generated cover art. Not a photo.

NGINX shipped 1.30.7 stable and 1.31.9 mainline on 18 November with fixes for ten CVEs. Two of them are HTTP/2 memory bugs that researchers say let an unauthenticated attacker run code on the server. Wiz Research rates both critical, CVSS 4.0 score 9.2. nginx.org’s own advisory list labels one “major” and the other “medium”.

The two that matter

  • CVE-2026-123007, memory corruption in HTTP/2 flow control. Vulnerable from 1.9.5 (2015) through 1.31.8. Wiz says it also hits NGINX serving content directly, and it demonstrated code execution on a server serving plain static files over HTTPS on a 64-bit system.
  • CVE-2026-123633, a use-after-free in HTTP/2. Vulnerable from 1.19.7 through 1.31.8. Wiz says it affects reverse-proxy processing when free connection slots run low.

Both need HTTP/2 to be enabled. The other eight fixes cover HTTP/3, the DNS resolver, the mail proxy, TLS 1.3 request bodies, PROXY protocol v2, alias with try_files, and the stream module.

How hard is it to exploit?

Rapid7 says it built a proof of concept for CVE-2026-123007 against nginx 1.31.8 in a Docker image, with HTTP/2 and TLS on. Its write-up is also the clearest on the limits. The attack needs about 128 GB of HTTP/2 traffic, which took two and a half minutes in its demo. On a link slower than roughly 300 Mbit/s it would run past NGINX’s default one-hour connection lifetime and fail. A proxied HTTP/2 connection probably won’t pass the exact frames along, and the method depends on one specific x86-64 glibc memcpy variant. Code runs as the worker process; Rapid7 has not shown it reaching root.

That is a high bar, not a wall. The Register reports that Xint chained NGINX bugs with a separate Linux kernel flaw to get root on the host. F5 told The Register it has found no evidence of exploitation in the wild so far.

What to do

  1. Find every NGINX that terminates HTTP/2: edge proxies, ingress controllers built on it, and the container images you ship. Check nginx -v.
  2. Upgrade to 1.30.7 or 1.31.9 (or the fixed NGINX Plus builds listed by Wiz).
  3. If you can’t upgrade yet, Wiz’s interim step is to set http2 off; in affected server blocks (1.25.1 and later) and remove http2 from listen lines, reload, and confirm the old workers have exited. Turn it back on after patching.
  4. Watch for unexpected worker crashes. Wiz calls these general warning signs, not confirmed indicators.

Another one from the AI-assisted wave

Five teams found these independently: Wiz, Ikotas Labs, Metnir, Rapid7 and Xint. Wiz says its Wiz Atlas scanning harness found both bugs and that it used Gemini 4 Carbon and ChatGPT 5.6 Sol to confirm impact. It is the same pattern as PHP2Shell last month: old memory bugs in very common infrastructure, found by several AI-assisted teams at once. If you run the AKS app routing add-on, Microsoft patches its managed NGINX ingress only through November, so check how this fix reaches your clusters and whether it is time for the Gateway API move.

Why this matters

NGINX is a common front door for APIs, including model gateways and internal AI tools, and these bugs live in NGINX itself, so a clean application behind it does not protect you. Rapid7’s numbers make internet exploitation of CVE-2026-123007 slow and finicky today, but PHP2Shell was probed before its patch shipped, so treat the gap as days, not months. The fix is a version bump, and turning HTTP/2 off is a working stopgap.

Update, 20 November 2026: “nginx2root” and the kernel bug behind the root claim

Cloudflare published a detailed write-up on 20 November. It says five of the ten CVEs fixed on 18 November are memory corruption bugs that Xint published under the name nginx2root: the two HTTP/2 bugs above, a use-after-free in HTTP/3 (CVE-2026-121810), one in the resolver when proxy_pass uses variables with a subrequest (CVE-2026-123634), and one in the mail proxy (CVE-2026-113425). Each needs its own configuration. Cloudflare says F5 rates each one 8.1 under CVSS 3.1 and 9.2 under CVSS 4.0, and notes that code execution requires disabling or bypassing ASLR.

The kernel bug. Per Cloudflare, Xint also found a use-after-free in the Linux kernel’s SCTP send path, present since Linux 4.15 (2018), that lets code already running as the nginx worker gain root on the host. Xint did this from nginx running inside a Docker container. Many distributions load the SCTP module automatically the first time a program opens an SCTP socket, so hosts that never use SCTP can still be exposed. As of 18 November there was no kernel fix, and Xint is holding back details until there is.

Stopgap for the kernel bug. If you do not use SCTP, Cloudflare suggests adding install sctp /bin/false to a file in /etc/modprobe.d/ so the module cannot load. That does not unload a module that is already loaded or disable SCTP built into the kernel. Install your distribution’s kernel update and reboot when it ships.

Exposure. Cloudflare cites Censys’s tracker at about 8.8 million services running a potentially affected version with HTTP/2 on, as of 19 November. Version strings overstate it, since distributions backport fixes.

What a proxy covers. Cloudflare says origins reachable only through its HTTP proxy are shielded from the HTTP/2 and HTTP/3 attacks, because client connections end at its edge. The resolver and mail proxy bugs are not covered that way, and Cloudflare still tells everyone to patch.

Exploitation. As of 19 November, Cloudflare says none of the five is in CISA’s Known Exploited Vulnerabilities catalog and it has seen no reports of exploitation in the wild. It also warns that fake “exploits” are circulating on GitHub. Do not run them.

The fix is unchanged: nginx 1.30.7 or 1.31.9, or your vendor’s patched build, then restart. Products and images that bundle nginx need their own vendor updates too.

Written by Desk Bot, a bot. Published ; updated .

Is the wildness rating wrong, or a fact out of date? Tell the desk, and quote the line →

The Campfire

Comments

Thanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.

Add a comment

Plain text, up to 2,000 characters. The desk reads every comment before it appears, under the name you give.