On November 18, 2026, CrowdStrike disclosed a set of five critical vulnerabilities in NGINX, a widely used open-source web server, collectively termed NGINX2Root. These vulnerabilities, particularly CVE-2026-123007 and CVE-2026-123633, enable unauthenticated remote code execution, allowing attackers to escalate privileges to root and escape Docker containers. Each of these vulnerabilities carries a CVSS score of 9.2, indicating their severity. F5 and the NGINX project released patches on the same day, underscoring the urgency for organizations to address these vulnerabilities.
Understanding NGINX2Root
NGINX2Root encompasses five vulnerabilities that facilitate remote code execution, along with a separate Linux kernel flaw that can be exploited to gain root access. The primary vulnerability, CVE-2026-123007, involves an integer underflow in NGINX’s HTTP/2 request-handling code. This flaw allows attackers to send specially crafted HTTP/2 traffic, leading to memory corruption within the NGINX worker process and enabling arbitrary command execution without authentication.
The critical aspect of NGINX2Root is the exploit chain it enables. Although the NGINX worker process typically runs under an unprivileged system account (like www-data or nginx), a second flaw in the Linux kernel’s SCTP networking subsystem can be exploited to escalate privileges to root. Researchers demonstrated a complete attack chain, including escaping a Docker container to access the underlying host system.
The attack sequence is as follows:
- An attacker sends crafted HTTP/2 frames to a public-facing NGINX instance without requiring credentials.
- Memory corruption in the NGINX worker allows code execution as the web server account.
- A Linux kernel SCTP flaw is exploited to elevate privileges from the worker account to root.
- The attacker escapes the Docker container to access the host system.
Additional vulnerabilities in the NGINX2Root set require specific configurations, such as 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 for CVE-2026-123007 is available, demonstrating that triggering the memory corruption requires transmitting approximately 128GB of HTTP/2 data. While this may limit mass exploitation, it does not preclude targeted attacks or future techniques that could lower the data requirement. Organizations should not delay patching based on this constraint.
Who Is Affected?
NGINX serves over a third of the world’s websites, making the impact of these vulnerabilities significant. The vulnerabilities affect various version ranges and configurations. For CVE-2026-123007 and CVE-2026-123633, HTTP/2 must be enabled. The following table summarizes the affected versions and conditions according to 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 should update to versions 37.3.0.1 (mainline) or 37.0.8.1 (stable). Notably, NGINX on Windows is not affected by this advisory, as it is considered beta software not intended for high-performance use.
Immediate Actions for Organizations
- Update NGINX to a patched release: Organizations should 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 as per the F5 advisory. It is essential to check downstream Linux distribution packages for updated versions.
- Restart NGINX after patching: A configuration reload does not replace the running binary. After installing the patched package, a full service restart is necessary to ensure the patched executable is in use.
- Implement temporary mitigations: Disabling HTTP/2 on affected listening ports can block CVE-2026-123007 and CVE-2026-123633, but this does not mitigate the other vulnerabilities. This measure should not replace patching.
- Inventory container images and third-party appliances: Any image built on a base layer that includes NGINX remains exposed. Organizations should rebuild images on patched base layers and check vendor advisories for updates.
- Prioritize internet-exposed instances: Hosts running NGINX with HTTP/2 enabled and reachable from the internet are at the highest risk and should be prioritized for patching.
Leveraging the CrowdStrike Falcon Platform
Exposure Management for Vulnerability Detection
The CrowdStrike Falcon® Exposure Management platform provides coverage for NGINX2Root vulnerabilities across various operating systems, including Linux and macOS. Customers can identify hosts exposed to NGINX2Root CVEs through the Falcon console, filtering by CVE ID to manage vulnerabilities effectively.
As organizations navigate the complexities of these vulnerabilities, timely patching and proactive security measures are essential to mitigate risks associated with NGINX2Root. For further details on the vulnerabilities and protective measures, refer to the CrowdStrike advisory here.


