Security · · 6 min read

NGINX2Root: Five NGINX Memory-Safety Bugs, Two of Them Unauthenticated HTTP/2 RCE (CVE-2026-123007, CVE-2026-123633)

F5 shipped nginx 1.31.9 and 1.30.7 on November 18, 2026. The worst bug, an HTTP/2 flow-control integer underflow, has been in the code since nginx 1.9.5 in 2015 and was shown to give code execution on a server that only serves static files. Upgrade, then restart. A reload does not load the new binary.

Muted editorial illustration of a tall arched stone gateway in a pale wall, with a thin crack running from the keystone through one of the two doors
Illustration by TechPulse Editorial · The front door was the weak point.
Severity
CRITICAL · CVSS 9.2
Affected
NGINX Open Source up to 1.31.8 (CVE-2026-123007 from 1.9.5, CVE-2026-123633 from 1.19.7, CVE-2026-121810 from 1.25.0, CVE-2026-123634 from 0.6.18, CVE-2026-113425 from 0.5.33 per nginx.org); NGINX Plus 37.x before the fixed builds
Patched
NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable); NGINX Plus 37.3.0.1 and 37.0.8.1 for CVE-2026-123007 (check F5 advisories for other CVEs and older Plus releases)

NGINX sits in front of a large share of the web as the TLS terminator, reverse proxy, load balancer and Kubernetes ingress. On November 18, 2026, F5 released nginx 1.31.9 (mainline) and 1.30.7 (stable) together with coordinated disclosures from Xint, Wiz Research, Rapid7, Metnir and Ikotas Labs. Several of these teams found the same bugs independently. Xint grouped five of them under the name NGINX2Root. Sophos and Wiz list each of the five at 9.2 under CVSS 4.0, while nginx.org’s own advisory page uses its usual major/medium labels.

The fix release also addresses several lower-severity issues, including a TLS 1.3 request-body infinite loop (CVE-2026-118899).

The five bugs

CVEWhat it isWhat you need to be exposedVulnerable (nginx.org)
CVE-2026-123007HTTP/2 flow-control integer underflow → invalid memcpy lengthHTTP/2 enabled on the listener1.9.5–1.31.8
CVE-2026-123633HTTP/2 connection use-after-freeHTTP/2 plus proxying to an upstream, with connection slots running low1.19.7–1.31.8
CVE-2026-121810HTTP/3 (QUIC) use-after-freeHTTP/3 plus proxying to an upstream1.25.0–1.31.8
CVE-2026-123634Resolver use-after-free during response processingproxy_pass to a server name with variables, plus an SSI or mirror subrequest that resolves the same name0.6.18–1.31.8
CVE-2026-113425Mail proxy use-after-freenginx configured as a mail proxy with auth_http0.5.33–1.31.8

The bugs are independent. An attacker needs only one exploitable path, not the whole set.

Why CVE-2026-123007 is the one to worry about

HTTP/2 flow control lets the client tell the server how many response bytes it may send. nginx tracks that credit per stream and per connection. Rapid7’s Stephen Fewer found that a client can cancel queued response data and make nginx return credit for bytes it never sent. The counter underflows. A later response is then copied with an invalid length, which corrupts memory in the worker.

What makes this bad:

  • The configuration is the default one. You only need http2 on a TLS listener. Wiz demonstrated code execution against nginx serving ordinary static files, with no backend application and no third-party modules.
  • It’s old. The bug has been in the code since nginx 1.9.5 (2015), when HTTP/2 support arrived. Xint says that as of November 10, 98.9% of hosts with an identifiable nginx version were affected.
  • ASLR doesn’t stop it. According to Sophos’s summary of F5’s advisories, code execution needs ASLR to be disabled or bypassed. Wiz and CIRCL point out that the researchers did bypass it, using the same bugs to read memory first.

Exploitation does have practical limits. Rapid7’s proof of concept against the official nginx 1.31.8 Docker image needed about 128 GB of HTTP/2 data. That took two and a half minutes in the lab, about two minutes on a 10 Gbit/s link and about seventeen minutes on 1 Gbit/s. Because nginx closes connections after one hour by default, anything slower than roughly 300 Mbit/s runs out of time. If an intermediary proxy re-frames HTTP/2, the exact frames the exploit depends on probably won’t reach nginx. Rapid7’s technique also relies on a specific glibc AVX-512 memcpy variant. These limits raise the bar, but they don’t remove the risk for well-connected targets.

From worker to root

On its own, each bug gives code execution as the nginx worker process, usually an unprivileged user. Xint went further and chained each one with a separate Linux kernel SCTP use-after-free/double-free (code from Linux 4.15) to bypass KASLR and get root on the host. That included escaping a Docker container, because containers share the host kernel. CIRCL notes that this kernel bug had no CVE ID as of November 18.

Where you don’t need SCTP, CIRCL describes blocking module loading with install sctp /bin/false in modprobe config. That doesn’t unload a module that is already loaded and does nothing if SCTP is built into the kernel.

What to do

  1. Upgrade NGINX Open Source to 1.31.9 or 1.30.7. For NGINX Plus, Rapid7 lists 37.3.0.1 and 37.0.8.1 as the fixed builds for CVE-2026-123007 and no fix for R34–R36; check the F5 advisories for the other CVEs.
  2. Restart, don’t just reload. Xint notes that nginx -s reload does not load the new binary. Confirm that old workers are gone.
  3. Find the hidden copies: ingress controllers, base images, appliances and vendor bundles that ship their own nginx. Distro packages may lag, especially on older releases.
  4. If you can’t patch today, set http2 off; on exposed server blocks (nginx 1.25.1+) and remove http2 from listen directives. That blocks CVE-2026-123007 and CVE-2026-123633, but not the HTTP/3, resolver or mail paths. For those, F5 advises avoiding SSI/mirror with variable upstream names and keeping mail proxy listeners on trusted networks.
  5. Watch for unexpected worker crashes and child processes spawned by nginx. Wiz says these are general warning signs, not confirmed indicators of compromise.

No in-the-wild exploitation had been reported at disclosure time. Given how many teams found the same bugs, and that Wiz says it used AI models to validate the impact, it would be unwise to assume that stays true for long.

Sources & Primary Advisories

  1. nginx.org — nginx security advisories
  2. Rapid7 — CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)
  3. Wiz Research — Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007
  4. Sophos X-Ops — Patches released for critical 'NGINX2Root' vulnerabilities
  5. CIRCL — TR-105 NGINX2ROOT: Remote Code Execution in NGINX and Potential Host Compromise
  6. Xint via Business Wire — PSA: Immediately Patch NGINX Web Servers
Share Dispatch