A decade-old flaw in NGINX HTTP/2 support can allow an unauthenticated attacker to execute arbitrary code on servers. The vulnerability, identified as CVE-2026-123007 and dubbed nginx2root, has been present in the open-source code since version 1.9.5 released on September 22, 2015.
F5, the company behind NGINX, released fixed versions 1.31.9 and 1.30.7 today. The flaw permits code execution when ASLR is turned off or can be bypassed. Security researchers at Wiz successfully bypassed ASLR and achieved code execution in their tests, while researchers at Xint executed code using nothing more than a reachable HTTP/2 port.
Code executed through the vulnerability runs with the privileges of an NGINX worker process. Elevating to root requires an additional privilege-escalation vector, according to CIRCL. In Xint tests, worker-level code obtained root via a separate Linux kernel SCTP bug, even inside a Docker container.
Affected Versions and Additional Flaws
Every open-source release from 1.9.5 through 1.31.8 is vulnerable. NGINX Plus versions 37.x before the fixed builds and R34 to R36 are also affected. The same updates address four more flaws that can lead to code execution under the same ASLR condition; all five issues received a CVSS 4.0 score of 9.2.
- CVE-2026-123007 requires HTTP/2 enabled
- CVE-2026-123633 requires HTTP/2 plus low worker_connections
- CVE-2026-123634 requires variable-built proxied server names with SSI or mirror subrequests
- CVE-2026-121810 requires HTTP/3 enabled
- CVE-2026-113425 requires NGINX used as a mail proxy
Rapid7 analysis indicates the attack needs roughly 128 GB of HTTP/2 traffic and takes about two and a half minutes in demonstration conditions.


