NGINX2Root: Identify and Protect with the CrowdStrike Falcon Platform

NGINX2Root refers to five nginx vulnerabilities, including CVE-2026-123007, that each allow remote code execution, and a separate Linux kernel flaw that can be chained with them to gain root.

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
CVEAffected Versions (per nginx Advisory)Fixed Versions (per nginx Advisory)Condition
CVE-2026-123007Nginx 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-123634Nginx 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-123633Nginx 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-121810Nginx 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-113425Nginx 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). 

Figure 1. Accessing vulnerability information within Falcon Exposure Management Figure 1. Accessing vulnerability information within Falcon Exposure Management

Coverage details:

  • Linux: The Falcon sensor identifies nginx installations via rpm and dpkg package managers on all sensor versions.
  • macOS: The Falcon sensor identifies nginx Homebrew installations.
  • NVA / Network Scan and EASM: Coverage uses banner-based detection relying on the nginx version string. Banner detection can miss hosts where the version string is suppressed or masked by a reverse proxy, CDN, or load balancer, and can produce false positives for Linux distribution packages that backport fixes without changing the reported version. Treat banner results as an indicator and validate them with host-based sensor results where possible.
  • Windows: nginx on Windows is not covered. The nginx project classifies its Windows port as beta software.

For exposure before vulnerability detections are released, customers can also search their internet-facing assets in EASM under Exposure Management > External Attack Surface > Assets, filtering by Application Name = nginx.

Figure 2. Accessing internet-facing asset information within Falcon Exposure Management Figure 2. Accessing internet-facing asset information within Falcon Exposure Management

A note on CVE IDs in the console: If CVE metadata for these identifiers is not yet visible, search by application name as an interim measure. Detections are released on a rolling basis as advisories are confirmed.

The Falcon Sensor Detects Post-Exploitation Activity

Exploitation of CVE-2026-123007 and CVE-2026-123633 occurs entirely within nginx worker memory through HTTP/2 traffic, as no file is written to disk and no process is launched at the exploit stage. The Falcon sensor's first detection opportunity is post-exploitation when the compromised nginx worker begins behaving in ways that deviate from normal web server activity.

Falcon monitors nginx process trees for the full range of attacker behaviors that follow a successful web-server compromise:

  1. Suspicious child processes: Shells and system utilities spawned under the nginx worker, including commands used for initial reconnaissance such as id, whoami, hostname, uname, and netstat
  2. Webshell activity: Script files written to web-accessible directories, including encoded and obfuscated variants commonly used to establish persistent access
  3. Credential access: Reads of sensitive system files such as /etc/passwd and /etc/shadow initiated from within the nginx process tree
  4. Download and staging: Use of common binaries to retrieve secondary payloads from external hosts, including raw IP addresses (commonly referred to as living off the land)
  5. Persistence: Modification of authorized keys via a shell spawned under the nginx worker
  6. Security tool interference: Attempts to stop, disable, or remove endpoint security software initiated from within a web-service process context
  7. Container-aware detections: Anomalous child processes and sensitive file access within containerized nginx deployments, including reads of sensitive system files by processes running inside a container under a webservice parent

Customers can review detections in the Falcon console under Endpoint Security > Activity > Detections. CrowdStrike recommends filtering by the affected host to scope results to systems running nginx and reviewing the process tree for each alert to understand the full scope of post-exploitation activity.

Falcon Next-Gen SIEM Identifies Threats

Falcon Next-Gen SIEM: Emerging Threat Response Dashboard

CrowdStrike Falcon® Next-Gen SIEM detection coverage for NGINX2Root (new “NGINX HTTP/2 RCE Vulnerabilities (CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425)” section on the CrowdStrike Falcon Emerging Threat Response dashboard) has been released to production as part of the NG-SIEM Content Packages release.

The Emerging Threat Response dashboard is a focused response tool designed to give CrowdStrike customers immediate visibility into active campaigns or newly discovered vulnerabilities that may impact their environment. By leveraging rich telemetry from Falcon platform modules and third-party data ingested in Falcon Next-Gen SIEM, this dashboard delivers ready-to-use detection and hunting queries that enable security teams to rapidly determine threat exposure and identify potentially compromised assets. 

NGINX2Root leaves no traditional indicators of compromise. There are no malicious file hashes, command-and-control domains, or IP addresses to match against. Detection is therefore entirely behavioral. The NGINX2Root section of the dashboard includes three coverage areas:

  • Post-exploitation hunting: A hunting widget that surfaces shell processes, interpreters, and living-off-the-land binaries spawned from an nginx worker process on Linux endpoints, the earliest observable signal after a successful exploit
  • Crash-burst detection: A widget that flags hosts where nginx workers crash 10 or more times within an hour, a pattern consistent with exploitation attempts triggering memory corruption before a stable payload is established. Organizations should treat this threshold as a starting point rather than a definitive signal. High-traffic or resource-constrained nginx deployments may generate worker crashes at elevated rates under normal conditions. Analysts should cross-reference crash-burst alerts against the post-exploitation hunting widget and Falcon Exposure Management data before concluding that exploitation has been attempted.
  • Exposure surface: A Falcon Exposure Management widget that surfaces assets potentially affected by the NGINX2Root CVEs, allowing analysts to cross-reference detection activity against confirmed vulnerable hosts

See Next-Gen SIEM > Log management > Dashboards

Figure 3. Identification of Emerging Threat Response dashboard within Falcon Next-Gen SIEM Figure 3. Identification of Emerging Threat Response dashboard within Falcon Next-Gen SIEM

Falcon for IT Remediates at Scale

CrowdStrike has released a dedicated Falcon for IT content pack for NGINX2Root that gives security and IT teams a single workflow to inventory affected hosts, assess HTTP/2 exposure, patch, and mitigate across Windows, macOS, and Linux. The content pack includes five tasks:

Query tasks (Windows, macOS, Linux):

  • NGINX HTTP2 Inventory: Discovers all nginx and NGINX Plus installations across the environment and reports version, platform, and HTTP/2 configuration status
  • NGINX HTTP2 Detection: Identifies hosts where nginx is vulnerable to CVE-2026-123007 and flags whether HTTP/2 is enabled, surfacing Priority Hosts (vulnerable with HTTP/2 on) for immediate action
  • NGINX HTTP2 Hunt: A targeted hunting query to scope hosts for further investigation

Action tasks (Linux only):

  • NGINX HTTP2 Update: Upgrades nginx to a patched release on Linux hosts where a fix is available. Both action tasks default to audit mode, which reports what would change without making any modifications to the host. Organizations should run in audit mode first and validate results before switching to enforce.
  • NGINX HTTP2 Mitigate: Disables HTTP/2 on affected Linux hosts as a temporary measure where immediate patching is not possible. Organizations running gRPC services on the same nginx listeners should note that disabling HTTP/2 also disables gRPC on those ports. Review application dependencies before enforcing this action in production.
Figure 4. NGINX HTTP/2 CVE-2026-123007 Content Pack in Falcon for IT Figure 4. NGINX HTTP/2 CVE-2026-123007 Content Pack in Falcon for IT

Automated remediation via the action tasks is available on Linux only. Windows and macOS customers should use the inventory and detection queries to identify affected hosts and apply patches manually per the guidance in the “What Should Organizations Do Now?” section above.

The pack includes a built-in dashboard with an Exposure Overview showing hosts scanned, impacted hosts, priority hosts, patched hosts, an HTTP/2 presence breakdown among impacted installs, and a top nginx versions chart. Falcon Exposure Management remains the primary source for vulnerability detection. The Falcon for IT detection query surfaces exposure context alongside remediation workflows and does not replace FEM CVE data.

Figure 5. Exposure Overview Dashboard in Falcon for IT Figure 5. Exposure Overview Dashboard in Falcon for IT

Understand Your Risk with CrowdStrike Counter Adversary Operations

CrowdStrike Counter Adversary Operations is monitoring adversary interest in NGINX2Root and has published threat intelligence on the associated vulnerabilities. No customer compromises attributable to NGINX2Root have been observed as of this publication. CrowdStrike will update this post if the situation evolves.

Widespread successful exploitation of these vulnerabilities is unlikely given their specific configuration requirements; however, threat actors will likely attempt to exploit CVE-2026-123007 in the immediate term as a public POC exists. Of the other four vulnerabilities, exploit developers will most likely target CVE-2026-123633 and CVE-2026-113425, as the remaining two (CVE-2026-121810 and CVE-2026-123634) require multiple uncommon configurations and dependencies. CVE-2026-123007 POC is unlikely to successfully achieve RCE as-is against a production server.

Conclusion and Recommendations

NGINX2Root is a critical disclosure affecting nginx installations across a wide range of versions and Linux distributions. The combination of unauthenticated initial access, a demonstrated root escalation chain, and container escape makes it a high-priority patching event for any organization running nginx with HTTP/2 enabled.

Organizations should:

  • Identify every nginx installation in their environment using Falcon Exposure Management, EASM, and manual inventory of container images and third-party appliances
  • Update to nginx 1.31.9 / 1.30.7 (Open Source) or 37.3.0.1 / 37.0.8.1 (nginx Plus) and restart nginx after patching
  • Temporarily disable HTTP/2 as a mitigation on systems that cannot be patched immediately (noting this does not cover all five CVEs)
  • Monitor Falcon behavioral alerts for web-server process anomalies, privilege escalation, and container escape activity
  • Watch for updated threat intelligence from CrowdStrike Counter Adversary Operations as in-the-wild exploitation develops

CrowdStrike will continue monitoring this threat and updating detections as new information becomes available.

1 https://technologychecker.io/technology/nginx


CrowdStrike Falcon Platform
Ready to protect your business?

Try CrowdStrike free today

Subscribe

Sign up now to receive the latest notifications and updates from CrowdStrike

See CrowdStrike Falcon in action