NGINX2Root: Five Critical NGINX RCE Flaws Chain Through HTTP/2 to Root — and an AI Found Them First

NGINX2Root: Five Critical NGINX RCE Flaws Chain Through HTTP/2 to Root — and an AI Found Them First

NGINX2Root: Five Critical NGINX RCE Flaws Chain Through HTTP/2 to Root — and an AI Found Them First

The web server that fronts roughly a third of the Internet just had a very bad week — publicly. On November 18, F5 released an out-of-band advisory and fixes for 22 NGINX vulnerabilities, five of them rated critical at CVSS 9.2 and collectively dubbed NGINX2Root: CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633 and CVE-2026-123634. All five can lead to unauthenticated remote code execution on a vulnerable server. Researchers found the flaws independently — Wiz, Ikotas Labs, Metnir and Rapid7 on one thread, and a discovery effort from security firm Xint, which also produced working exploit demonstrations, including a full chain from anonymous HTTP/2 request to root on the host by combining NGINX with a separate Linux kernel SCTP bug that escapes the NGINX Docker container.

The two headline flaws sit in HTTP/2. CVE-2026-123007 is a flow-control bug in the HTTP/2 implementation that NGINX has carried since it added the protocol in 2015 — it affects every version from 1.9.5 through 1.31.8. Crafted traffic pushes the flow-control window past its allowed threshold into a heap buffer overflow, corrupting worker memory. An attacker can crash the worker, leak memory addresses and overwrite the pointer to a cleanup function that fires when a connection closes — "this can be used to execute commands with worker privileges and receive the output over an existing connection," Xint's advisory reads. Wiz demonstrated unauthenticated RCE on a server hosting ordinary static files over HTTP/2 with TLS; on systems with ASLR disabled, the code-execution step is easier. CVE-2026-123633 is a use-after-free affecting versions 1.19.7 onward when NGINX accepts HTTP/2 connections and proxies to a backend — so the classic reverse-proxy that fronts most web applications is squarely in scope. The other three are use-after-frees in narrower paths: HTTP/3 reverse proxying (CVE-2026-121810), DNS resolution with subrequests (CVE-2026-123634) and mail proxy authentication (CVE-2026-113425).

Exposure numbers explain the urgency. Censys' live tracker puts roughly 8.8 million NGINX services in the affected version band with HTTP/2 enabled as of November 19, with over 511,000 already patched or mitigated — and 104 million more that don't disclose versions at all. A Shodan scan found that about 66% of NGINX HTTPS endpoints support HTTP/2, and 98.9% of version-disclosing NGINX servers were running a version inside the CVE-2026-123007 range. SecurityWeek notes proof-of-concept exploits have already gone public. Fixes landed in NGINX Open Source 1.31.9 and corresponding NGINX Plus releases, so exposure is really a function of how fast your distro or image ships the patch. The discovery method matters too: Xint used AI-driven vulnerability research to find the set — the same AI-accelerated discovery wave that surfaced PHP2Shell, the Apache mod_http2 flaw and this week's Java4Shell, which is why the interval between "disclosed" and "exploited" keeps shrinking.

What Should You Do?

  1. Upgrade to NGINX 1.31.9 or your distro's backported equivalent immediately — out-of-band means do not wait for your normal patch cycle. NGINX Plus customers should apply the corresponding release.
  2. Inventory HTTP/2 and HTTP/3 listeners. CVE-2026-123007 needs an HTTP/2 listener an attacker can reach; CVE-2026-123633 additionally needs proxying to a backend. Any public reverse-proxy matches both.
  3. Check whether containers save you — they don't. Xint's chain escapes an NGINX Docker container through a kernel SCTP flaw to reach host root. Treat NGINX in a container as exposed, not isolated, until both NGINX and the host kernel are patched.
  4. Verify ASLR status and disable h2 as a stopgap. On hosts you cannot patch today, removing listen ... http2 (and http3 where present) from public listeners closes the two worst data-plane paths at the cost of protocol features.

The WAF Angle

NGINX2Root is a reminder that the WAF platform is itself a web server with an HTTP parser — and when the parser has a memory bug, the thing doing the filtering becomes the thing being owned. Worse, these flaws are data-plane: there is no suspicious payload signature to match, just protocol-legal HTTP/2 traffic that overflows a window counter. That said, the incident is also a WAF argument: an RCE in the front door's parser is exactly the class of attack where a separate filtering tier with a different codebase buys survival time. The earlier mod_http2 RCE in Apache and HTTP2Shell in Node.js tell the same story — HTTP/2 implementations across the stack keep generating pre-auth memory corruption, so run your edge and your filter on different parsers, and patch both.

Sources