The Decade-Old Shadow: NGINX HTTP/2 Vulnerability Exposes Infrastructure Roots

What Happened?
A severe vulnerability, identified as CVE-2026-123007 and dubbed 'nginx2root,' has been discovered in NGINX's HTTP/2 implementation. This flaw, which has persisted in the codebase since September 2015, enables unauthenticated attackers to execute arbitrary code on vulnerable servers.
The issue affects open-source versions 1.9.5 through 1.31.8, as well as multiple NGINX Plus releases. Researchers from Wiz and Xint successfully demonstrated that the flaw allows code execution inheriting NGINX worker permissions, which, when chained with kernel-level exploits, can escalate to full host root access even within containerized environments.
Why It Matters
The longevity of this vulnerability highlights a significant risk in widely deployed web server infrastructure. Because NGINX powers a massive portion of the global internet, the ability for remote, unauthenticated actors to bypass Address Space Layout Randomization (ASLR) and potentially gain root privileges presents a catastrophic risk to data integrity and system availability.
While no in-the-wild exploitation has been reported, the public availability of proof-of-concept code creates an immediate window of exposure. Organizations must treat this as a high-priority remediation effort, especially given that a standard reload of NGINX is insufficient—a full binary restart is mandatory to patch the flaw.
Key Details & Takeaways
- Vulnerability duration: The flaw persisted for over 10 years, spanning versions released since September 22, 2015.
- Multi-vector risk: Four additional vulnerabilities rated at 9.2 CVSS 4.0 were patched simultaneously, covering HTTP/3, mail proxy, and SSI/mirror subrequests.
- Remediation requirement: Simple configuration reloads are ineffective; organizations must perform a full restart or live binary upgrade to versions 1.31.9 or 1.30.7.