Karen IT Security Response Center (KSRC) Advisory
Advisory ID: KSRC-2026-11182 | Publication Date: 18 November 2026
Critical Unauthenticated Remote Code Execution in NGINX HTTP/2
CVE-2026-123007 (nginx2root / NGINX2Shell)
Summary
A critical unauthenticated remote code execution vulnerability has been disclosed in NGINX’s HTTP/2 implementation. Tracked as CVE-2026-123007 and commonly referred to as nginx2root or NGINX2Shell, the flaw allows an attacker to execute arbitrary code on vulnerable NGINX servers without authentication.
The vulnerability carries a CVSS v4.0 score of 9.2 (Critical) and affects a very wide range of NGINX versions dating back to 2015. A public proof-of-concept exploit is already available.
Technical Overview
CVE-2026-123007 is an integer underflow in NGINX’s HTTP/2 flow-control code. When processing specially crafted HTTP/2 traffic, the flow-control window can exceed permitted limits, leading to an out-of-bounds memory copy (heap-based buffer overflow). This memory corruption can result in:
- Remote code execution as the NGINX worker process
- Denial of Service (worker process crash)
- Information disclosure / memory leakage (useful for ASLR bypass)
The only required condition is that HTTP/2 is enabled. The vulnerability is exploitable even on servers serving only static content — no backend application or third-party modules are needed.
A related high-severity issue, CVE-2026-123633 (use-after-free in HTTP/2 connection handling), was fixed in the same releases and also carries a CVSS 9.2 rating.
Affected Systems
- NGINX Open Source: 1.9.5 through 1.31.8
- NGINX Plus: Versions prior to the fixed builds listed below
Fixed versions:
- NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline)
- NGINX Plus 37.0.8.1 and 37.3.0.1
Note: Some Linux distributions may ship backported packages. Always verify the actual package version rather than relying solely on nginx -v.
Exploitation Status
- Public proof-of-concept (including full RCE chain) has been published by Rapid7.
- Multiple independent research teams (Wiz, Xint, Rapid7 and others) have confirmed unauthenticated remote code execution.
- No confirmed widespread in-the-wild exploitation reported at the time of this advisory, but the combination of public PoC + unauthenticated RCE significantly elevates risk.
Recommendations
- Immediate Action: Upgrade all NGINX instances to 1.30.7 (stable) or 1.31.9 (mainline), or the corresponding fixed NGINX Plus builds.
- After upgrading, perform a full restart of NGINX (a simple reload is not sufficient to replace the running binary).
- Inventory all NGINX servers and confirm whether HTTP/2 is enabled (
http2in listen directives orhttp2 on;). - Prioritize internet-facing and high-value servers.
- If immediate patching is not possible, consider temporarily disabling HTTP/2 as a short-term mitigation (note: this may impact performance and client compatibility).
- Monitor for anomalous HTTP/2 traffic patterns and unexpected worker process crashes.
Given the unauthenticated nature of the vulnerability, the existence of public exploit code, and the extremely wide affected version range, this update should be treated as a high-priority emergency patch.
Support from KSRC
KSRC (Karen IT Security Response Center) is fully prepared to assist organizations with any questions, technical guidance, or incident-related issues arising from these vulnerabilities.
Whether you require help with version assessment, patch planning, or response coordination, our team is available.
Karen IT
We make the Internet harder to abuse.