NGINX2Root flaws let attackers hijack web servers

Five critical flaws in NGINX, the web server software that powers a large share of the world's websites, can let an attacker run code on a vulnerable server without logging in. Researchers have shown the most serious of the flaws can be chained with a separate Linux kernel bug to gain full root access on the host.
The flaws were disclosed on 18 November 2026 by F5, the company behind NGINX, in an out-of-band security release. They have been given the collective name NGINX2Root by the researchers who found them. Fixes are available now, and administrators are being urged to install them or switch off the affected features until they can.
A decade-old flaw at the centre
The most urgent flaw is tracked as CVE-2026-123007. It is a flow-control bug in NGINX's HTTP/2 code that can corrupt memory inside a worker process. It has been present since NGINX 1.9.5, released in September 2015, so every open-source release from 1.9.5 through 1.31.8 is affected. An attacker only needs the server to have HTTP/2 enabled and reachable.
Researchers at Wiz demonstrated unauthenticated remote code execution against a server hosting ordinary static files over HTTP/2 with TLS. Researchers at Xint, also known as Theori, went further, chaining the flaw with a separate, unpatched flaw in the Linux kernel's SCTP subsystem to escape an NGINX Docker container and gain root privileges on the underlying host. The kernel flaw has no CVE identifier yet.
Code run through the NGINX flaw on its own gets the permissions of the NGINX worker process. Reaching root on the host takes the second flaw, which is why the researchers describe the chain, rather than either bug alone, as the route to full takeover.
Five flaws, one patch
CVE-2026-123007 is one of five critical remote code execution flaws fixed in the same release. The second, CVE-2026-123633, is a use-after-free flaw that affects NGINX when it accepts HTTP/2 connections and proxies requests to a backend server, and can trigger when a worker runs low on connection slots. It affects versions 1.19.7 through 1.31.8.
The other three are CVE-2026-121810, a use-after-free flaw in HTTP/3 reverse proxying; CVE-2026-123634, a use-after-free flaw in DNS resolution with subrequests; and CVE-2026-113425, a use-after-free flaw in mail proxy authentication. F5 rates each of the five as Critical, with a CVSS 4.0 score of 9.2. The same release also fixed five further NGINX flaws, including CVE-2026-118899, a high-severity issue that can send a worker into an infinite loop while reading a request body over TLS 1.3.
The flaws were found independently by several research teams. F5 credits Xint, Wiz, Rapid7, Ikotas Labs and Metnir for the HTTP/2 flaws, and Palo Alto Networks Unit 42 among the reporters of the second flaw. Proof-of-concept code for CVE-2026-123007 is publicly available on GitHub, although researchers note it is constrained and suited only to demonstrating the attack against a freshly started container on the same machine.
How exposed is the internet?
No attacks exploiting the flaws have been reported so far, and the flaws are not listed in CISA's Known Exploited Vulnerabilities catalog. That does not mean the risk is theoretical: the researchers have working demonstrations, and the proof of concept is public.
Security researcher Florian Roth said the flaws were worse than the recent Node2Shell and Java2Shell flaws, but did not appear to be an imminent threat for most NGINX deployments, because exploitation depends on the server's configuration. Xint reported that 98.9 percent of NGINX hosts disclosing recognisable versions were running software in the affected range, although that figure does not account for whether HTTP/2 is enabled or whether fixes have been backported. Censys, the internet scanning company, counted about 8.8 million NGINX services potentially exposed to CVE-2026-123007 as of 19 November, and said more than 511,000 previously exposed services had already been patched or mitigated.
What to do now
The fix is in NGINX Open Source 1.30.7 for the stable branch and 1.31.9 for the mainline branch. NGINX Plus users should update to 37.0.8.1 or 37.3.0.1. Administrators who cannot patch immediately should disable HTTP/2 until they can, although that step only covers the two HTTP/2 flaws and not the HTTP/3, resolver or mail proxy flaws.
Cloudflare, which published its own analysis on 20 November, said origins behind its HTTP proxy are shielded from the HTTP/2 and HTTP/3 attacks because it terminates those connections at its edge, but added that patching is still necessary. The safest course for any exposed NGINX server is to update, restart, and then check whether the server was reachable while unpatched.