In short: nginx has two critical vulnerabilities nicknamed “nginx2root” (CVE-2026-123007 and CVE-2026-123633). They let attackers run code on the web server without logging in. Almost every nginx version from the last ten years is affected, but only when HTTP/2 is enabled. The fix is in nginx 1.30.7 (stable) and 1.31.9 (mainline). If you run nginx on a VPS or root server, check it today.
What happened
According to BleepingComputer, several security teams (Xint, Wiz, Ikotas Labs, Metnir and Rapid7) found the two HTTP/2 bugs independently. F5, the company behind nginx, fixed them together with further vulnerabilities.
- CVE-2026-123007 is a bug in HTTP/2 flow control that can corrupt the memory of an nginx worker. All versions from 1.9.5 (released in 2015) to 1.31.8 are affected. Wiz showed that a server delivering nothing but static files over HTTP/2 with TLS is enough.
- CVE-2026-123633 is a use-after-free bug. It hits nginx when it accepts HTTP/2 connections and forwards requests to a backend (reverse proxy). Versions 1.19.7 to 1.31.8 are affected.
The worrying part: Xint chained the first flaw with a separate bug in the Linux kernel's SCTP subsystem. That let the researchers break out of an nginx Docker container and gain root on the host, hence the name “nginx2root”.
No public exploits exist so far: Wiz is holding back its proof-of-concept code for now. The same F5 update fixes three more use-after-free flaws (HTTP/3 proxying, DNS resolution with subrequests, mail proxy) and five further bugs, including CVE-2026-118899, which lets an attacker push nginx into an infinite loop over TLS 1.3 (denial of service).
How dangerous is it really?
Security researcher Florian Roth considers the flaws serious, but does not see an imminent threat for most nginx setups. Judging exposure from the version number alone is misleading, he says. What matters is the configuration:
- HTTP/2 enabled and reachable from outside: yes, affected until patched.
- Also used as a reverse proxy (e.g. nginx in front of PHP-FPM over HTTP, Node.js, Apache or a game server panel): CVE-2026-123633 applies as well.
- HTTP/2 disabled: not attackable through the two “nginx2root” flaws. Install the update anyway because of the other bugs.
According to Censys, about 8.8 million nginx services were potentially exposed on 19 November, based on version and HTTP/2 support.
What you should do now
- Check the version:
nginx -v. Anything up to and including 1.31.8 is in the affected range. - Is HTTP/2 on?
nginx -T 2>/dev/null | grep -n http2. If you seelisten … http2orhttp2 on;, HTTP/2 is active. - Update:
apt update && apt upgrade(Debian/Ubuntu) ordnf upgrade nginx(Rocky, AlmaLinux), thensystemctl restart nginx. Distributions often backport fixes into their own package version, so the version number does not have to jump to 1.30.7. Your distribution's security advisory is what counts. At the time of writing (19 Nov 2026), Debian 12 had not yet released a fixed package. - No update yet? Turn off HTTP/2 for now. On older versions remove
http2from thelistenlines (listen 443 ssl;); from nginx 1.25.1 sethttp2 off;. Then runnginx -t && systemctl reload nginx. Your sites keep working over HTTP/1.1. Note: this only protects against the two “nginx2root” flaws, not the others. - nginx in Docker: update the container image too and keep the host kernel current, because the root chain goes through a kernel bug.
What we at NexoraHost say
nginx is part of many of your setups: as a web server, as a reverse proxy in front of PHP or Node.js, and often in front of game server panels. Our own website and our web hosting (Plesk) use nginx too. We take care of those systems; web hosting customers don't need to do anything.
On your VPS and root servers you are the admin. We don't install updates there without asking, because that could interrupt your services. If you are unsure whether your server is affected, or run into problems after turning off HTTP/2: open a ticket.
VPS → · Root server Linux · Web hosting · Apache vs. nginx · Source: BleepingComputer
More blog articles
In short: The PHP team has fixed 17 security vulnerabilities. Seven are rated critical, and five could even let attackers run their own code. The good news: the critical flaws can only be exploited under certain conditions, not on a default installation. You should update an...
In short: Apache's HTTP/2 module has a critical vulnerability (CVE-2026-119618). An unauthenticated attacker can use it to run code on the server with the privileges of the web server process. Versions 2.4.55 to 2.4.70 are affected, but only when HTTP/2 is enabled. A fix is...
Short version: On 8 September 2026 Microsoft shipped the largest Patch Tuesday so far – about 974 CVEs, including two actively exploited zero-days and several critical bugs in Remote Desktop (RDP). If you run a Windows V-Server or root server, update today and reboot. Not “s...