What is NGINX2root?
NGINX2root (CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425) is a collection of Remote Code Execution vulnerabilities in NGINX. CVE-2026-123633 is a Use-after-Free issue in how NGINX handles HTTP/2 connections when it is configured as a reverse proxy and is running low on available connection slots.
A specially crafted request can crash the NGINX worker process, and in some cases, be leveraged to gain code execution.
| CVE | Description | CVSS | Exploited in the wild |
|---|---|---|---|
| CVE-2026-123633 | Remote Code Execution in NGINX “NGINX2root” | 9.2 Critical (CVSS 4.0) | Not reported |
| CVE-2026-123007 | Remote Code Execution in NGINX “NGINX2root” | 9.2 (v4.0) | Not reported |
| CVE-2026-123634 | Remote Code Execution in NGINX “NGINX2root” | 9.2 (v4.0) | Not reported |
| CVE-2026-121810 | Remote Code Execution in NGINX “NGINX2root” | 9.2 (v4.0) | Not reported |
| CVE-2026-113425 | Remote Code Execution in NGINX “NGINX2root” | 9.2 (v4.0) | Not reported |
Is NGINX2root being exploited in the wild?
As of November 19, 2026, no exploitation in the wild has been reported.
How did NGINX2root come to light?
Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently found the NGINX2root vulnerabilities and reported them to F5, the company behind NGINX. Wiz reported the use-after-free that became CVE-2026-123633 to F5 on October 21, 2026, and F5 confirmed another research team had already reported the same issue. F5 supplied a review patch on November 10, 2026, and shipped its public security release, covering CVE-2026-123633 and the related CVEs, on November 18, 2026.
How is watchTowr helping NGINX “NGINX2root” customers?
- Adversary Sight engine identified NGINX “NGINX2root” instances across client environments and assessed exposure.
- Rapid Reaction identified exposure to this vulnerability across the watchTowr client base, giving teams the time they need to act.
What is NGINX “NGINX2root”?
NGINX is a widely used web server that many organizations run as a reverse proxy in front of websites and APIs. It receives incoming requests, forwards them to the right backend application, returns the response to users, and can also serve content directly or balance traffic across multiple servers.
Which NGINX “NGINX2root” versions are affected?
| Product | Affected Versions | Fixed Version |
|---|---|---|
| NGINX OSS (CVE-2026-123633) | 1.19.7 and later | 1.30.7, 1.31.9 |
| NGINX OSS (CVE-2026-123007) | 1.9.5 and later | 1.30.7, 1.31.9 |
| NGINX Plus (CVE-2026-123633) | R33, 37.0.0 and later | 37.0.7.1, 37.2.0.1 |
| NGINX Plus (CVE-2026-123007) | R33, 37.0.0 and later | 37.0.8.1, 37.3.0.1 |
- NGINX must have HTTP/2 enabled for client connections for NGINX2root to be exploitable.
- The server must be configured as a reverse proxy that forwards client requests to a backend application.
- The worker process handling the connection must be running low on available worker_connections slots.
- Running code instead of just crashing the process requires an attacker to bypass ASLR, or for it to be disabled or bypassable.
Security teams should prioritize NGINX deployments that are internet-facing and have HTTP/2 enabled, since those servers face the most immediate and direct exposure to this exploit chain.
How do I fix NGINX2root?
Fixed versions were released on November 18, 2026 that fix the vulnerabilities and the associated “NGINX2root” chain. Affected organizations should upgrade to the latest version where possible. As a mitigation, disabling HTTP/2 removes the condition exploitation relies upon.
- Identify every NGINX deployment that has HTTP/2 enabled for client connections.
- Check which of those deployments are actively configured as a reverse proxy to a backend application.
- Upgrade to the latest NGINX release, or apply associated security patches on affected systems.
- Disable HTTP/2 on any deployment that cannot be updated right away.
- Confirm address space randomization is active on the host operating system where possible.
What types of threat actors typically exploit these vulnerabilities?
No attribution has been made public.
