Back to threat alerts

NGINX2Root (CVE-2026-123007 & Related Flaws)

NGINX2Root is a collection of five critical memory-corruption vulnerabilities ( tracked as CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425 ) affecting NGINX Open Source and NGINX Plus releases from version 1.9.5 onward. Disclosed on November 18, the lead flaw resides in NGINX's HTTP/2 flow-control implementation. Researchers at Xint and Wiz demonstrated pre-authentication remote code execution (RCE) against default HTTP/2 over TLS configurations across AWS, GCP, and Azure, and Xint further chained this worker-level access with an unpatched Linux kernel SCTP vulnerability to achieve full host root; including breaking out of Docker containers.

Threat alert
November 19, 2026

CVE-2026-123007 is an integer underflow and heap-based out-of-bounds read/write vulnerability in NGINX's HTTP/2 module (ngx_http_v2_module, introduced in NGINX 1.9.5 in September 2015) that affects any server with HTTP/2 over TLS enabled. Each of the five NGINX2Root flaws is rated 9.2 (Critical) under CVSS v4.0 and 8.1 (High) under CVSS v3.1 by F5.
‍

When NGINX queues HTTP/2 response DATA frames, it reserves connection-level send credit. Exploitation unfolds across three stages:

  • Unsigned Credit Overflow & Underflow: If an attacker replenishes connection credit to its maximum limit via WINDOW_UPDATE while DATA remains queued, and then cancels the stream (via RST_STREAM or SETTINGS_INITIAL_WINDOW_SIZE), NGINX refunds the reserved credit during request cleanup without bounds validation—pushing the unsigned counter above its maximum. A subsequent 13-byte WINDOW_UPDATE check performs an unsigned subtraction that underflows, allowing repeated WINDOW_UPDATE frames to amplify the counter into the upper half of its 64-bit unsigned range.
  • Signed Type Cast & Out-of-Bounds Heap Corruptions: When the buffered TLS output filter casts this value to a signed 64-bit integer (off_t), it interprets the window as negative and passes an enormous copy length to memcpy.
  • ASLR Bypass & Control-Flow Hijacking: The oversized memcpy triggers out-of-bounds heap reads and writes that leak memory pointers (bypassing ASLR) and overwrite a connection cleanup function pointer to execute arbitrary commands when the connection closes.
    ‍

Alongside CVE-2026-123007, the November 18 disclosure resolves four additional NGINX2Root Use-After-Free (UAF) RCE paths and five further NGINX vulnerabilities:

  • CVE-2026-123633 (HTTP/2 UAF RCE) & CVE-2026-121810 (HTTP/3 UAF RCE): Triggered when worker_connections slots run low on an NGINX reverse proxy.
  • CVE-2026-123634 (DNS Resolver UAF RCE): Triggered when a variable-based proxy_pass is paired with the mirror or SSI modules.
  • CVE-2026-113425 (Mail Proxy UAF RCE): Affects ngx_mail_proxy_module configurations utilising auth_http.
  • CVE-2026-118899 (TLS 1.3 Infinite Loop DoS): Rated 7.5 (High) under CVSS v3.1, leading five additional fixes and affecting NGINX 1.13.0 and later during TLS 1.3 request-body processing.
Weaponisation & Attack Surface

Although active exploitation has not been reported in the wild and none of the flaws appear in CISA's Known Exploited Vulnerabilities (KEV) catalogue as of November 19, 2026, the vulnerabilities support three distinct adversarial impact tiers that vary sharply in technical barrier and prerequisites:

  • Unauthenticated Worker Crash & Denial of Service: Requires no ASLR bypass or precision heap layout. Malformed HTTP/2 flow-control manipulation or triggering the TLS 1.3 infinite loop (CVE-2026-118899) immediately crashes or stalls NGINX worker processes (SIGSEGV / signal 11).
  • Pre-Authentication Worker Remote Code Execution: Achieving command execution as the nginx or www-data worker requires leaking heap addresses to bypass ASLR and overwriting a connection cleanup function pointer. While Xint and Wiz demonstrated full remote command execution over public HTTPS endpoints on AWS, GCP, and Azure, Rapid7's public PoC (sfewer-r7/CVE-2026-123007) notes that its specific heap-amplification technique requires transferring roughly 128 GB of HTTP/2 traffic over ~2.5 minutes (requiring links faster than ~300 Mbit/s to complete before NGINX's 1-hour connection timeout) and relies on a glibc memory-copy routine selected on x86-64 CPUs with avx512f and avx512vl support.
  • Container Escape & Host Root Privilege Escalation : Once executing inside the unprivileged NGINX worker context, attackers can chain a separate, currently unpatched Use-After-Free flaw in the Linux kernel's Stream Control Transmission Protocol (SCTP) send path (present since Linux kernel v4.15) to elevate privileges to host root and escape standard Docker containers.

Exposure Scope & Visibility Blind Spots

Pre-authentication exposure for CVE-2026-123007 arises wherever an externally reachable NGINX listener negotiates HTTP/2 (h2 via TLS ALPN), which is enabled by default across roughly two-thirds of HTTPS NGINX servers and managed platforms such as Laravel Forge. In a November 10, 2026 Shodan snapshot, 11.8 million of 11.94 million version-identifiable NGINX hosts (98.9%) ran builds in the affected version range, and 88.6% of Fortune 500 companies utilise NGINX.

  • Upstream CDN / Proxy Shielding: Origins reachable exclusively through an upstream CDN or load balancer (such as Cloudflare with proxied DNS records) that terminates HTTP/2 and HTTP/3 at the edge and forwards HTTP/1.1 to the origin are shielded from external HTTP/2 exploitation.
  • WAF & Logging Blind Spots: Standard WAF URL and body inspection rules cannot detect or block the low-level HTTP/2 control frames (WINDOW_UPDATE, RST_STREAM) used in the attack, and these control frames are not recorded in standard NGINX access.log files.
Vulnerable Versions and Affected Releases

The NGINX2Root vulnerabilities affect upstream NGINX Open Source across the Stable (0.5.15 / 1.9.5 through 1.30.6) and Mainline (1.31.0 through 1.31.8) branches, as well as commercial NGINX Plus releases R33 through 37.2.0.1.

Because Linux distribution packages and container images frequently backport security fixes without incrementing the base version string reported by nginx -v, administrators must verify full package version strings against vendor security trackers using dpkg-query or rpm -qa.

Across managed Ubuntu and cloud infrastructure, Laravel Forge servers require explicit manual intervention: Forge does not update NGINX via Ubuntu unattended upgrades, and instances provisioned prior to April 27, 2026 rely on Ondřej Surý's ondrej/nginx PPA—which has been removed from Launchpad and must be migrated to the official nginx.org repository to receive patched builds.


Product / Track

Vulnerable Versions

First Fixed Build

Operational & Packaging Notes

NGINX Open Source (Stable)

0.5.15 / 1.9.5 to 1.30.6

1.30.7

HTTP/2 flaw present from 1.9.5 onward.

NGINX Open Source (Mainline)

1.31.0 to 1.31.8

1.31.9

Patch released Nov 18, 2026.

NGINX Plus (Commercial)

R33 to 37.2.0.1

37.0.8.1 / 37.3.0.1

Coordinate updates via F5 advisory.

Laravel Forge / Ubuntu PPA

Legacy ondrej/nginx builds

1.30.7 / 1.31.9

Defunct PPA; migrate to nginx.org repo.
‍
Recommendations and Mitigations

Operators should apply interim configuration changes and package migrations carefully, as orphaned module directives from third-party PPAs can prevent NGINX from starting, and soft reloads (nginx -s reload) leave the vulnerable binary active in memory.

To remediate exposure systematically across hosts, containers, and edge infrastructure, execute the following steps in order:

  1. Patch NGINX Releases, Migrate Legacy PPAs, and Perform a Full Service Restart: Upgrade NGINX Open Source to 1.30.7 or 1.31.9 and NGINX Plus to 37.0.8.1 or 37.3.0.1, and rebuild container images pinned to older base tags.
    1. On Ubuntu or Laravel Forge hosts still pointing to the defunct ondrej/nginx PPA, remove /etc/apt/sources.list.d/ondrej-ubuntu-nginx-* directly (do not run add-apt-repository --remove), configure the official nginx.org repository with pin priority 900, and upgrade via sudo apt-get install --only-upgrade -o Dpkg::Options::=--force-confold nginx (commenting out orphaned load_module lines for brotli, geoip, image-filter, xslt, or ssl-ct if startup fails).
    2. ‍Critical: Do not rely on nginx -s reload; execute sudo systemctl restart nginx to replace the in-memory binary and verify /proc/<pid>/exe no longer points to a (deleted) executable.
  1. Disable Vulnerable Directives and Block Kernel SCTP Where Patching Is Delayed: For environments awaiting distribution backports, maintenance windows, or migration off EOL operating systems (such as Ubuntu 20.04 LTS), disable HTTP/2 (http2) and HTTP/3 (http3) on internet-facing listeners. Concurrently replace variable-based proxy_pass paired with mirror or SSI directives, restrict mail proxy listeners to trusted internal networks, and blacklist the sctp Linux kernel module via /etc/modprobe.d/ to block the container-escape and root privilege-escalation chain.
  2. Enforce Edge HTTP/2 Termination and Process/Crash Telemetry Monitoring: Route external traffic through an upstream CDN or load balancer (such as Cloudflare with proxied DNS records) that terminates client HTTP/2 and HTTP/3 connections at the edge and forwards strictly HTTP/1.1 to the NGINX origin, while firewalling direct origin IP access. Concurrently monitor EDR and auditd telemetry for child processes spawned by nginx or www-data worker UIDs, modprobe sctp executions, spikes in exited on signal 11 (SIGSEGV) or worker_connections are not enough messages in NGINX error.log, and long-lived TLS connections transferring tens of gigabytes of traffic with near-zero logged HTTP requests.

‍

Resources:
  • https://nginx2root.com/
  • https://radar.cloudflare.com/zero-wire/nginx2root
  • https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html
  • https://laravel.com/forge/docs/knowledge-base/nginx-to-root