All articles
ArticlesNovember 19, 20266 min read

nginx HTTP/2 RCE (CVE-2026-123007): check and patch now

The nginx HTTP/2 RCE bug CVE-2026-123007 affects every release since 2015. How to check if HTTP/2 is on, which versions fix it, and a stopgap config.

nginxcve-2026-123007nginx http/2 rcehttp/2remote code executionf5nginx2rootapplication security
nginx HTTP/2 RCE (CVE-2026-123007): check and patch now

On November 18, 2026, F5 disclosed an nginx HTTP/2 RCE bug, CVE-2026-123007, and released nginx 1.31.9 and 1.30.7 to fix it. The flaw sits in nginx's HTTP/2 code, needs no login, and has been there since HTTP/2 support arrived in version 1.9.5 in 2015.

It is the second pre-auth memory bug in core infrastructure in two days, after Java4Shell on November 17, and it reaches further. Netcraft's September 2026 survey counted nginx on 225 million sites.

I'm a security engineer at erxes, and nginx is the piece I expect to find in front of almost any self-hosted app, usually installed once and then forgotten. Here is who is exposed, how to check, and what to do if a patched package isn't available yet.

What the nginx HTTP/2 RCE bug is

HTTP/2 has flow control. Each side tells the other how much data it may send, and nginx keeps that allowance in a counter. Rapid7's write-up sums up the bug in one line:

nginx can miscalculate how much response data an HTTP/2 client has allowed it to send.

— Stephen Fewer, Rapid7

According to Wiz Research's analysis, when a client cancels a stream that still has data queued, nginx returns the unused allowance to the connection without checking it against the protocol maximum. A later response is then copied with a bad length. The CVE record describes the result as a heap buffer overflow, typically followed by a worker crash, with code execution possible when ASLR is disabled or the attacker can bypass it.

Bypassing it turned out to be doable. Wiz says it confirmed remote code execution with an ASLR bypass on official nginx 1.31.7 and 1.31.8 builds, on a server that only served static files.

F5 scores the bug 8.1 under CVSS 3.1 and 9.2 (critical) under CVSS 4.0, with attack complexity marked high in both. The nginx.org advisory list labels it "major".

The same release fixes a second HTTP/2 bug, CVE-2026-123633. It is a use-after-free that needs nginx to accept HTTP/2 from clients, proxy requests to a backend, and have a worker running low on worker_connections. It carries the same scores and affects 1.19.7 through 1.31.8. The 1.31.9 changelog lists ten security fixes in total.

On names: Xint calls the set NGINX2Root and Ikotas Labs calls the HTTP/2 flaw NGINX2Shell, while Wiz and Rapid7 use only the CVE IDs. Search by CVE number.

Who is exposed to CVE-2026-123007

Two things have to be true: a vulnerable version, and HTTP/2 enabled on a port clients can reach.

ProductAffectedFixed in
nginx Open Source, mainline1.31.0 to 1.31.81.31.9
nginx Open Source, stable and older1.9.5 to 1.30.61.30.7
NGINX Plus 37.1 and 37.237.1.0 to 37.2.0.137.3.0.1
NGINX Plus 37.037.0.0 to 37.0.7.137.0.8.1

Rapid7's table lists no fix for NGINX Plus R34 to R36. Those installs have to move to a fixed 37.x build.

The nginx documentation says the HTTP/2 module is not built by default and the http2 directive defaults to off. I wouldn't lean on that. Packaged builds usually include the module, and http2 shows up in nearly every TLS config template. Check:

nginx -v
nginx -V 2>&1 | grep -o with-http_v2_module
nginx -T 2>/dev/null | grep -n 'http2'
curl -sI --http2 -o /dev/null -w '%{http_version}\n' https://your-host/

The first three show the version, whether the HTTP/2 module is compiled in, and where it is switched on. The last one, run from outside your network, prints 2 if the server negotiates HTTP/2 with clients.

Then look for the nginx you didn't install yourself. Container images, ingress controllers and appliances often bundle their own copy and follow their supplier's patch schedule.

Distribution packages backport fixes without changing the upstream version string, so compare the full package version against your distro's advisory. Don't assume the package manager already has the fix either. When I checked the Debian security tracker early on November 19, bookworm, trixie, forky and sid were all still listed as vulnerable.

How to fix it

Upgrade to a fixed build, then restart nginx. A configuration reload starts new workers from the binary that is already running, so a reload after the package update leaves you on the old code. Restart the service, do a live binary upgrade, or redeploy the containers from a patched image. Then confirm the version on every instance. The easy miss is a box that was upgraded but never restarted.

If you can't patch today

Turn off HTTP/2 on client-facing listeners. On nginx 1.25.1 and later:

server {
    listen 443 ssl;
    http2 off;
}

Also remove the http2 parameter from any listen directive. On versions older than 1.25.1, removing that parameter is the whole change. Reload, confirm the old workers have exited, then run the curl check again and expect 1.1.

This has a cost. Pages with many small assets load slower without multiplexing, and gRPC stops working because it needs HTTP/2. It also covers only the two HTTP/2 bugs, so the other fixes in the release still need the upgrade.

How hard CVE-2026-123007 is to exploit

Rapid7 published a proof of concept that works against an nginx 1.31.8 Docker image with HTTP/2 and TLS enabled. Its write-up is candid about the limits:

  • The exploit sends about 128 GB of HTTP/2 data over one connection. That takes two minutes on a 10 Gbit/s link and seventeen minutes at 1 Gbit/s.
  • Below roughly 300 Mbit/s, it runs into nginx's default one-hour connection lifetime and fails.
  • Code runs with the worker's permissions. Rapid7 says execution as root "has not been established".
  • If the HTTP/2 connection passes through a proxy, the attacker's frames probably won't arrive in a usable form.

That list explains the "high" attack complexity. I don't read it as a reason to wait.

Seventeen minutes at 1 Gbit/s is within reach of any rented cloud VM. The proxy point only helps if your origin can't be reached directly. And these are the limits of one exploit. Wiz built its own and is keeping it private:

In the interest of customer protection, we will not be releasing these exploits at this time.

— Wiz Research

As for attacks, NetSPI's notice says no exploitation in the wild had been reported, and neither CVE was in CISA's Known Exploited Vulnerabilities catalog as of its November 18 release.

For detection, Wiz suggests investigating unexpected worker crashes (in the error log, lines like worker process 1234 exited on signal 11) and commands launched by nginx. It also points at long-lived HTTP/2 connections that move very large amounts of data.

Four teams found the same bug

The CVE record credits four separate reporters for CVE-2026-123007: Stephen Fewer of Rapid7, Tomer Schwartz of Wiz Research, Xint.io, and Ikotas Labs, whose credit line reads "using GPT-6 Astra". Wiz says its AI tool, Atlas, discovered both HTTP/2 bugs.

The vulnerable code sat in nginx for eleven years. Then four teams reported it in time for the same patch, at least two of them using AI. When discoveries collide like that, I assume people who don't file reports are reading the same code with the same tools.

The patch is public too, and I wrote two days ago about agents turning patches into exploits.

So today I'd list every nginx I run, including the ones inside images. I'd patch the internet-facing ones first and switch HTTP/2 off wherever a patched package doesn't exist yet. Then restart, and check from the outside.

FAQ

Is nginx vulnerable if HTTP/2 is disabled?

Not to CVE-2026-123007 or CVE-2026-123633, which both require HTTP/2. The same release fixes eight other security issues, so upgrade anyway.

Which nginx version fixes CVE-2026-123007?

nginx Open Source 1.31.9 (mainline) and 1.30.7 (stable), released on November 18, 2026. For NGINX Plus the fixed builds are 37.3.0.1 and 37.0.8.1.

Is CVE-2026-123007 being exploited in the wild?

No public report says so as of November 18, 2026, and it is not in CISA's Known Exploited Vulnerabilities catalog. A public proof of concept from Rapid7 exists.


Sources

Cover image: nginx logo, Wikimedia Commons

Related articles