nginx2root: five nginx vulnerabilities and how to protect your server

What happened
On 18 November five vulnerabilities were disclosed in nginx that allow remote code execution on a server without a password or an account. All five were found by Xint researchers, and the main one was also found independently by Wiz, Rapid7 and Ikotas Labs. Xint named the series nginx2root: it also includes a Linux kernel bug described below. Fixes were released the same day in nginx 1.30.7 and 1.31.9.
The most dangerous one is CVE-2026-123007, a flaw in HTTP/2 flow control. It affects versions 1.9.5 to 1.31.8, which means almost any nginx since 2015. Having HTTP/2 enabled is enough, even if the server only serves static files. The other four are triggered by specific settings:
- CVE-2026-123633 — HTTP/2 when nginx proxies requests to a backend.
- CVE-2026-121810 — HTTP/3 (QUIC).
- CVE-2026-123634 —
resolvertogether with aproxy_passwhose address is built from variables, when the request goes throughmirroror SSI. - CVE-2026-113425 — the nginx mail proxy, the
mailblock.
On its own, the vulnerability lets an attacker run code with the rights of the nginx worker process. But chained with a new bug in the Linux kernel SCTP module, the attack gives root, including an escape from a Docker container to the server itself. The kernel bug has been there since version 4.15 and has neither a CVE number nor a fix yet.
There are no confirmed attacks yet, according to CERT-EU. But a proof-of-concept exploit for CVE-2026-123007 has already been published, so do not put this off.
What we did
We checked our own infrastructure. Where nginx accepted HTTP/2 from the internet, we turned it off, and we blocked the SCTP module on all nodes. We install nginx updates as packages come out.
Who is affected
Anyone running nginx on their VPS: from distribution or nginx.org packages, in Docker or as part of other software, such as a website control panel. The main vulnerability is triggered when HTTP/2 is enabled. It is turned on by the http2 parameter of a listen line or, in nginx 1.25.1 and later, by the http2 on; directive.
Note that even nginx listening only on a local address is vulnerable if another program in front of it forwards connections from the internet as is, without decrypting them.
How to check
sudo nginx -v— the nginx version. From nginx.org and in Docker, 1.30.7 and 1.31.9 are fixed. Distributions usually fix their own version without changing the number: Ubuntu 24.04 still shows 1.24.0 after the update.apt-cache policy nginxon Debian and Ubuntu,dnf info --installed nginxon AlmaLinux and Rocky Linux,apk list -I nginxon Alpine — where the package comes from and its full version. If it comes from your distribution, compare it with the fixed one in the section below.sudo nginx -T | grep -E "http2|quic"— every mention of HTTP/2 and HTTP/3 in the active configuration, including all included files. HTTP/2 is on if the output hashttp2 onor thehttp2parameter in alistenline, HTTP/3 if alistenline hasquic.
If nginx runs in Docker, run the same commands via docker exec <name> and check every container with nginx.
How to update
Fixed builds are available from nginx.org and in the official Docker image. Distributions are releasing their own packages one by one, below is the status as of 19 November.
- nginx from nginx.org:
sudo apt update && sudo apt install nginxon Debian and Ubuntu,sudo dnf upgrade nginxon AlmaLinux and Rocky Linux. - Docker:
docker compose pull && docker compose up -d. Thenginx:stableandnginx:latestimages are already updated, and if your compose file pins a version, set 1.30.7 or 1.31.9. Rebuild your own nginx-based image:docker compose build --pull && docker compose up -d. - Ubuntu: fixed packages are out for all supported releases: 1.18.0-6ubuntu14.23 in 22.04, 1.24.0-2ubuntu7.20 in 24.04, 1.28.3-2ubuntu1.13 in 26.04 and 1.30.4-7ubuntu1.2 in 26.10. Update with
sudo apt update && sudo apt upgrade. For 20.04 and older, the fix is only available through Ubuntu Pro. - AlmaLinux 9 and 10: the stock nginx is fixed in advisories ALSA-2026:A025 (1.20.1-32.el9_9.1.alma.3) and ALSA-2026:A024 (1.26.3-16.el10_3.1.alma.2). Update with
sudo dnf upgrade. The advisories only cover the two HTTP/2 vulnerabilities, so protect against the rest through settings. nginx from AlmaLinux 9 module streams (dnf module) has no fix yet. - Alpine: fixed in 3.22 and 3.23 (1.28.3-r8) and in 3.24 (1.30.7-r0). As root, update with
apk update && apk upgradeand restart nginx:rc-service nginx restart. 3.21 and older will not get a fix because they are no longer supported: move to a newer release and close the vulnerabilities through settings until then. - Debian: there is no fix for 12 and 13 yet, it is being prepared. Until it is out, close the vulnerabilities through settings as described below, then update with
sudo apt update && sudo apt upgrade. Debian 11 is no longer supported and will not get a fix. - RHEL, Rocky Linux and AlmaLinux 8: no fix yet. Close the vulnerabilities through settings and update with
sudo dnf upgradeonce the advisory is out. In version 8 of these systems, only the nginx:1.24 stream will get the fix, while the default 1.14 stream and the other streams are no longer supported: if your nginx comes from one of them, move to nginx:1.24 or to the nginx.org packages. - A control panel or other software with its own nginx: update it once its developer releases a fix, and until then close the vulnerabilities through settings.
With distribution packages, update the whole system rather than just the nginx package: modules, such as the mail one, live in separate packages. After updating, restart nginx: sudo systemctl restart nginx. A reload is not enough: it rereads the settings, but the old nginx code stays in memory. In Docker no separate restart is needed, docker compose up -d recreates the container itself.
If you cannot update yet
Without an update, each vulnerability is closed by its own setting:
- HTTP/2 (CVE-2026-123007 and CVE-2026-123633). Remove the
http2parameter from alllistenlines, and in nginx 1.25.1 and later also addhttp2 off;to everyserverblock. gRPC stops working without HTTP/2: if yours goes through nginx, do not delay the update. - HTTP/3 (CVE-2026-121810). Remove the
listenlines with thequicparameter and addhttp3 off;andadd_header Alt-Svc 'clear' always;so that browsers stop using HTTP/3. - resolver (CVE-2026-123634). Do not use
mirroror SSI together with aproxy_passwhose address is built from variables. - Mail proxy (CVE-2026-113425). Open the nginx mail ports only to trusted networks.
Then apply the settings: sudo nginx -t && sudo systemctl reload nginx, a reload is enough here. Use sudo nginx -T | grep -E "http2|quic" to make sure no http2 on is left and no listen line has the http2 or quic parameter.
Block the SCTP module
This is worth doing even after updating nginx: the kernel bug is not fixed yet, and most servers do not use the SCTP module.
echo "install sctp /bin/false" | sudo tee /etc/modprobe.d/disable-sctp.conf
The block only applies to new loads of the module. Check whether it is already loaded: sudo lsmod | grep sctp. If the command prints anything, reboot the server. Containers need no separate setting: they share the kernel with the server.
More in the nginx security advisories, the CERT-EU advisory, the Wiz write-up and the Xint publication.