A set of five critical vulnerabilities in nginx, one of the most widely deployed open-source web servers, was disclosed on November 18, 2026. 

Collectively branded NGINX2Root by researchers, these flaws allow an unauthenticated remote attacker to execute code on a target host and, in a demonstrated exploit chain, escalate to root and escape a Docker container to reach the underlying host. The two most severe CVEs (CVE-2026-123007 and CVE-2026-123633) each carry a CVSS 4.0 score of 9.2. F5 and the nginx project released patches the same day.

This post explains who is affected, what organizations should do now, and how the CrowdStrike Falcon® platform helps identify exposed assets and detect post-exploitation activity.

What Is NGINX2Root?

NGINX2Root is the name researchers gave to five nginx vulnerabilities that each allow remote code execution, plus a separate Linux kernel flaw that can be chained with them to gain root. The headline flaw is CVE-2026-123007, an integer underflow in nginx’s HTTP/2 request-handling code. HTTP/2 is the modern web protocol enabled by default in most production nginx deployments. When an attacker sends specially crafted HTTP/2 traffic, the flaw corrupts memory inside the nginx worker process and allows arbitrary command execution with no authentication or user interaction required.

What elevates the severity of NGINX2Root is the chain it enables. The nginx worker process runs as an unprivileged system account, typically www-data or nginx. While that account alone does not have root access, a second flaw in the Linux kernel’s SCTP networking subsystem can be reached from the compromised worker and exploited to escalate privileges to root. Researchers demonstrated the full chain end-to-end, including escaping a Docker container running nginx to reach the underlying host.

The attack chain in brief:

  1. Attacker sends crafted HTTP/2 frames to a public-facing nginx instance with no credentials required
  2. Memory corruption in the nginx worker yields code execution as the webserver account
  3. A Linux kernel SCTP flaw elevates privileges from the worker account to root
  4. The attacker escapes the Docker container to reach the host system

Additional CVEs round out the NGINX2Root set, each requiring different but common configurations: specific reverse proxy and resolver settings (CVE-2026-123634), HTTP/2 with upstream forwarding (CVE-2026-123633), HTTP/3 with upstream forwarding (CVE-2026-121810), and mail proxy mode (CVE-2026-113425).

A public proof-of-concept is available for CVE-2026-123007. Triggering the memory corruption requires transmitting approximately 128GB of HTTP/2 data (roughly two minutes over a 10 Gbit/s connection). This limits opportunistic mass internet exploitation today, but it does not prevent targeted attacks, exploitation from within a network, or future techniques that reduce the data requirement. Organizations should not treat this constraint as a reason to delay patching.

Who Is Affected?

Nginx is estimated to serve more than a third of the world’s websites.1 The five CVEs affect different version ranges and configuration conditions. HTTP/2 must be enabled for CVE-2026-123007 and CVE-2026-123633, which are the most severe. The table below summarizes affected versions and conditions per the official nginx advisory.

Table 1. Affected versions and conditions for the five NGINX2Root CVEs, per the official nginx advisory
CVE Affected Versions (per nginx Advisory) Fixed Versions (per nginx Advisory) Condition
CVE-2026-123007 Nginx Open Source:

>1.31.0 – 1.31.8

1.9.5 – 1.30.6

Nginx Plus:

37.1.0 – 37.2.0.1

37.0.0 – 37.0.7.1

R34 – R36

Nginx Open Source:

1.31.9

1.30.7

Nginx Plus:

37.3.0.1

37.0.8.1

(no R branch patch)

HTTP/2 enabled
CVE-2026-123634 Nginx Open Source:

1.31.0 – 1.31.8

1.0.0 – 1.30.6

0.6.18 – 0.8.55

Nginx Plus:

37.1.0 – 37.2.0.1

37.0.0 – 37.0.7.1

R34 – R36

Nginx Open Source:

1.31.9

1.30.7

(no 0.x branch patch)

Nginx Plus:

37.3.0.1

37.0.8.1

(no R branch patch)

Uses resolver, request-derived proxy_pass, and mirror with mirror_request_body off
CVE-2026-123633 Nginx Open Source:

1.31.0 – 1.31.8

1.19.7 – 1.30.6

Nginx Plus:

37.1.0 – 37.2.0

37.0.0 – 37.0.6.1

R34 – R36

Nginx Open Source:

1.31.9

1.30.7

Nginx Plus:

37.2.0.1

37.0.7.1

(no R branch patch)

HTTP/2 with requests forwarded to an upstream server
CVE-2026-121810 Nginx Open Source:

1.31.0 – 1.31.8

1.25.0 – 1.30.6

Nginx Plus:

37.1.0 – 37.2.0.1

37.0.0 – 37.0.7.1

R34 – R36

Nginx Open Source:

1.31.9

1.30.7

Nginx Plus:

37.3.0.1

37.0.8.1

(no R branch patch)

HTTP/3 with requests forwarded to an upstream server
CVE-2026-113425 Nginx Open Source:

1.31.0 – 1.31.8

0.5.33 – 1.30.6

Nginx Plus:

37.1.0 – 37.2.0

37.0.0 – 37.0.7

R33 – R36

Nginx Open Source:

1.31.9

1.30.7

Nginx Plus:

37.3.0.1

37.0.8.1

(no R branch patch)

Mail proxy using proxy on and auth_http

NGINX Plus customers: fixed versions are 37.3.0.1 (mainline) and 37.0.8.1 (stable). No fix is available on the R branch.

Note that nginx on Windows is not affected by this advisory. nginx itself labels its Windows port as beta software not intended for high-performance use.

What Should Organizations Do Now?

  1. Update nginx to a patched release: Apply nginx Open Source 1.31.9 or later (mainline branch) or 1.30.7 or later (stable branch). nginx Plus customers should update to 37.3.0.1 or 37.0.8.1 per the F5 advisory. Downstream Linux distribution packages (Red Hat, Debian, Ubuntu, Amazon Linux, and others) are being updated; check your distribution’s security advisories for per-package fixed versions.
  2. Restart nginx after patching: A configuration reload (nginx -s reload) replaces the configuration but does not replace the running binary. After installing the patched package, perform a full service restart to ensure the patched executable is running.
  3. As a temporary mitigation: Disabling HTTP/2 on affected listening ports blocks CVE-2026-123007 and CVE-2026-123633. This mitigation does not cover CVE-2026-123634, CVE-2026-121810, or CVE-2026-113425. It is not a substitute for patching.
  4. Inventory container images and third-party appliances: Any image built on a base layer that includes nginx, and any appliance whose vendor has not yet released a patch, remains exposed. Rebuild images on patched base layers and check vendor advisories.
  5. Prioritize internet-exposed instances: Hosts running nginx with HTTP/2 enabled that are reachable from the internet carry the highest immediate risk. Prioritize these for patching.

How the CrowdStrike Falcon Platform Helps

Falcon Exposure Management Uncovers Exposed Assets

CrowdStrike Falcon® Exposure Management coverage for NGINX2Root is available across Linux, macOS, NVA/Network Scan, and external attack surface management (EASM).

Customers can find hosts exposed to NGINX2Root CVEs in the Falcon console under Exposure Management > Vulnerability Management > Vulnerabilities, then filter by CVE ID (CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, or CVE-2026-113425). 


Share.

Comments are closed.