Key Facts
- Industry name: NGINX2root
- CVE: CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425
- CVSS: 9.2 Critical (CVSS 4.0)
- Exploited in the wild: Not reported as of November 19, 2026
- Fix available: Yes
- Last updated: November 19, 2026
What Is NGINX2root?
NGINX2root (CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425) is a set of Remote Code Execution vulnerabilities in NGINX that let an unauthenticated, external attacker execute code. CVE-2026-123633 is a use-after-free issue in how the software handles HTTP/2 connections, and CVE-2026-123007 is an integer underflow in HTTP/2 flow-control accounting. Both vulnerabilities require HTTP/2 to be enabled for the affected server.
The vulnerabilities affect a mix of NGINX versions, including CVE-2026-123007 affecting NGINX dating back to version 1.9.5, released in 2015. F5 released a security update on November 18, 2026, that includes fixes for the issues covered here.
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.
| 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?
As of November 19, 2026, no exploitation in the wild has been reported.
What Is NGINX “NGINX2root”?
NGINX is a web server and reverse proxy that enterprises use to receive incoming traffic, terminate HTTPS connections, and route requests to the applications and APIs behind it. It can also serve web content directly and balance traffic across multiple servers. An attacker who compromises the server running NGINX can execute code, access sensitive data passing through it, alter websites, or disrupt the services it fronts.
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 |
Is Your NGINX “NGINX2root” Affected?
- The affected NGINX server must have HTTP/2 enabled for the vulnerabilities to be exploitable.
- CVE-2026-123007 affects versions of NGINX dating back to version 1.9.5, released in 2015.
- CVE-2026-123633 affects reverse-proxy processing when available connection slots on the server run low.
- CVE-2026-123007 can also affect NGINX serving content directly, without a backend application.
How to Fix NGINX2root
Security teams should apply patches / security updates released on November 18, 2026, which fix the vulnerabilities in NGINX. If upgrading immediately is not possible, disable HTTP/2 on affected servers until the update can be installed.
- Identify every NGINX deployment that has HTTP/2 enabled.
- Apply the security updates released on November 18, 2026, to all affected servers.
- Disable HTTP/2 temporarily on any server that cannot be updated right away.
- Prioritize internet-facing NGINX deployments that attackers can reach directly.
- Review NGINX configurations to confirm HTTP/2 is only enabled where it is required.
How watchTowr Is Helping Clients
The watchTowr Platform delivers Preemptive Exposure Management, identifying, validating, and mitigating external exposure across enterprise environments.
- 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.
Request a demo to see how Rapid Reaction identifies exposure to emerging threats like NGINX2root (CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425).
