Approximately 8.8 million NGINX services were potentially exposed to CVE-2026-123007 as of November 19, according to Censys’ live exposure tracker — a figure that crystallizes why the newly disclosed "nginx2root" flaws demand immediate attention.
The two nginx2root defects and how they work
Two critical HTTP/2 vulnerabilities, collectively labeled "nginx2root," allow unauthenticated attackers to execute code remotely on vulnerable NGINX web servers. The first, CVE-2026-123007, is described as a flow-control bug that can corrupt memory in an NGINX worker; it affects versions from 1.31.8 down to 1.9.5 (released in 2015). The second, CVE-2026-123633, is a use-after-free issue that manifests when NGINX accepts HTTP/2 connections and proxies requests to a backend; it impacts versions 1.19.7 through 1.31.8.
According to published demonstrations, exploiting CVE-2026-123007 can yield unauthenticated remote code execution against servers serving ordinary static files over HTTP/2 with TLS. CVE-2026-123633 can be abused when the worker runs low on connection slots and closes an active connection, freeing memory that a still-in-flight request continues to use — a use-after-free condition that also led to an RCE demonstration.
Who found the flaws and what they demonstrated
The vulnerabilities were discovered independently by multiple research teams: Xint, Wiz, Ikotas Labs, Metnir, and Rapid7. Wiz demonstrated unauthenticated remote code execution against an HTTPS HTTP/2 endpoint but is not publicly releasing its proof-of-concept exploits at this time. Xint went further in its public demonstration, showing how CVE-2026-123007 can be chained with a separate Linux kernel bug to achieve root access.
Xint reported that the accompanying kernel vulnerability affects the Linux kernel's SCTP subsystem and can be used to escape an NGINX Docker container and gain root privileges on the underlying host. Censys ran lab tests and reproduced the underlying memory corruption conditions in four of the five flaws the researchers reported, though Censys did not achieve remote code execution during its testing.

This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildOther vulnerabilities fixed alongside nginx2root
F5 — the company behind NGINX — addressed the nginx2root defects in its security update and also fixed additional issues discovered by researchers. Besides CVE-2026-123007 and CVE-2026-123633, F5 fixed three more use-after-free vulnerabilities: CVE-2026-121810 (HTTP/3 reverse proxying), CVE-2026-123634 (DNS resolution with subrequests), and CVE-2026-113425 (mail proxy authentication).
F5’s update also covers five other vulnerabilities not highlighted in the initial researcher reports. The most notable of those is CVE-2026-118899, a high-severity defect that allows an unauthenticated attacker to drive an NGINX worker into an infinite loop while reading a request body over TLS 1.3, resulting in denial of service.
Patching, mitigation, and recommended action
F5 released fixes in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). NGINX Plus users should update to versions 37.0.8.1 or 37.3.0.1. System administrators are advised to upgrade immediately to the latest NGINX release or, if an immediate upgrade is not possible, to temporarily disable HTTP/2 — a mitigation that covers only the two nginx2root flaws that require HTTP/2 to be enabled on a reachable listener.
Wiz’s public restraint on PoC publication and Censys’ inability to reproduce RCE in lab conditions underscore that practical exploitation depends on environment and configuration. Nevertheless, the ability to achieve unauthenticated RCE in at least one demonstration and to chain NGINX exploitation with a kernel SCTP bug to escalate to host root highlights the stakes for exposed systems.
What this means for system administrators, container hosts, and enterprise NGINX users
- System administrators: Verify whether your NGINX instances accept HTTP/2 connections on externally reachable listeners and prioritize updates to the fixed NGINX releases. If patching cannot be performed immediately, disable HTTP/2 to mitigate the two nginx2root flaws.
- Container and host operators: Review kernel hardening and SCTP subsystem exposure on hosts running NGINX in containers. Xint’s demonstration of chaining an NGINX exploit with a Linux kernel SCTP bug to escape a Docker container and obtain root privileges shows container escape is a real concern where both software stacks are unpatched.
- Enterprise NGINX (NGINX Plus) customers: Move quickly to the NGINX Plus builds F5 cited (37.0.8.1 or 37.3.0.1) and confirm whether vendor or distribution backports have already been applied to deployed systems.
Security researcher Florian Roth summarized the exposure assessment on X: "it's worse than Node2Shell and Java2Shell, but doesn’t appear to be an imminent threat for most NGINX deployments." Roth also warned against inferring widespread exposure from version numbers alone, noting that exploitation requires HTTP/2 to be enabled and other configuration conditions to be met. Xint has reported that 98.9% of NGINX hosts that disclose recognizable versions ran within the affected ranges, but Censys notes that 104 million services do not disclose their versions, complicating broad exposure estimates. Censys also reports more than 511,000 services that were previously exposed have already been patched or mitigated.
The practical takeaway is straightforward: where HTTP/2 is enabled on externally reachable listeners, apply the updates from F5 now or disable HTTP/2 until you can. For environments running NGINX in containers or on hosts where the kernel SCTP subsystem is reachable, broaden the patching scope to include the kernel fixes or mitigations cited by your vendor.




