New NGINX HTTP/2 flaw lets attackers take over web servers without logging in
NGINX released versions 1.30.7 (stable) and 1.31.9 (mainline) on November 18. They fix ten vulnerabilities, and the worst of them, CVE-2026-123007, allows remote code execution (RCE): an attacker who has never logged in can run code on a web server that has HTTP/2 enabled. The flaw has been in the code since version 1.9.5 in 2015 and affects every release up to 1.31.8, according to the NGINX security advisories. Five research teams found it independently: Wiz, Xint, Rapid7, Ikotas Labs and Metnir.
What the HTTP/2 bug does
HTTP/2 lets each side tell the other how much data it may send, and NGINX keeps that number in a counter. A crafted sequence of flow-control updates pushes the counter past its limit. NGINX then works with an invalid length and copies data outside the intended memory area. Wiz rates the bug 9.2 out of 10 on the CVSS 4.0 scale and says it confirmed code execution, including a bypass of ASLR address randomization, on the official 1.31.7 and 1.31.8 builds, the company wrote. A server that only serves static files over HTTPS is enough. A second HTTP/2 bug, CVE-2026-123633, frees a connection while a request is still running and hits NGINX working as a reverse proxy. Wiz gives it the same 9.2 score.
From a web visitor to root on the host
Xint went further. In research it calls nginx2root, its team chained CVE-2026-123007 with a flaw in the Linux kernel's SCTP subsystem that has existed since kernel 4.15 in 2018 and has no patch yet. In the demonstration, the attack escaped a Docker container running NGINX and gained root on the underlying AWS host over its public IP address, Xint says. The company also confirmed the NGINX bug on Google Cloud and Azure. Xint found the flaws on October 11 and reported them to F5, which owns NGINX, on October 16. Besides the two HTTP/2 bugs, its list includes use-after-free flaws in the DNS resolver (CVE-2026-123634), in HTTP/3 (CVE-2026-121810) and in the mail proxy (CVE-2026-113425).
Wiz and Xint both kept their working exploits to themselves, and no attacks have been reported so far. Last month NGINX fixed another batch of code execution flaws, and last week Apache closed a similar hole in its HTTP/2 code.
How many servers are exposed
On November 10 Shodan listed 56.7 million hosts running NGINX. About 11.94 million of them showed a version number, and 98.9% of those fell in the vulnerable range. Xint notes that this does not prove each one can be attacked: HTTP/2 has to be on, and Linux distributions often backport fixes without changing the version that nginx -v prints. Distribution packages are lagging behind. On November 18 the Debian security tracker still marked NGINX as vulnerable in every supported release.
The update also matters for people who run their own VPN on a rented server. Many such setups put NGINX in front of the tunnel to handle TLS or to show an ordinary website to anyone who opens the address, and that NGINX is exposed to the internet just like a regular site.
What administrators should do
- Update: install NGINX 1.30.7 or 1.31.9, or your distribution's patched package once it appears, and restart NGINX. A reload keeps the old binary running.
- Turn off HTTP/2 until then: on NGINX 1.25.1 and newer, set
http2 off;in each server block. On older versions, removehttp2from thelistenlines. This blocks the two HTTP/2 bugs, but not the other three. - Block the kernel module: on servers that do not use SCTP, add
install sctp /bin/falseto a file in/etc/modprobe.d/. This does not unload a module that is already loaded. - Check the package, not the banner: compare the full package version with your distribution's security advisory.