Dev.to Security 🔐 Cybersecurity 👁 0 📖 2 min read

nginx2root (CVE-2026-123007): How to Check and Patch Your nginx Server

On November 18, 2026, nginx released versions 1.30.7 (stable) and 1.31.9 (mainline) with ten security fixes. Five of them, found by the security firm Xint, are known as nginx2root. The worst, CVE-2026-123007, is an integ

On November 18, 2026, nginx released versions 1.30.7 (stable) and 1.31.9 (mainline) with ten security fixes. Five of them, found by the security firm Xint, are known as nginx2root. The worst, CVE-2026-123007, is an integer overflow in nginx's HTTP/2 flow-control code that has existed since nginx 1.9.5 in 2015. F5 rates it 9.2 out of 10.

On a server with HTTP/2 switched on, an attacker without any login can send crafted WINDOW_UPDATE messages, corrupt memory and run commands as the nginx worker process. The other four nginx2root bugs need specific features: HTTP/2 or HTTP/3 in front of a backend, the resolver directive with subrequests, or the mail proxy.

Your version number can mislead you. Ubuntu and Debian backport fixes without changing the version, so a patched Ubuntu 24.04 still reports nginx 1.24.0. Check the package changelog instead:

zcat /usr/share/doc/nginx-common/changelog.Debian.gz | grep -m1 CVE-2026-123007

A matching line means you're patched. On Ubuntu 24.04, the fixed package is 1.24.0-2ubuntu7.20.

To fix it: run your distro's update (apt install --only-upgrade nginx nginx-common, or dnf update nginx), or move to 1.30.7 or 1.31.9, or pull the new Docker image. Then restart nginx rather than just reloading it, so no old worker keeps running the vulnerable code.

Can't patch today? Set http2 off; (nginx 1.25.1 and later) or remove http2 from your listen lines. Browsers fall back to HTTP/1.1; only gRPC needs HTTP/2.

The "root" in the name comes from a separate, still-unpatched Linux kernel SCTP bug that Xint chained with the nginx flaw to take over the whole machine. If you don't use SCTP, block the module with install sctp /bin/false in a file under /etc/modprobe.d/.

A public proof of concept appeared on November 18, though no attacks had been reported as of November 19. With millions of exposed servers, patch this week.

Sources

This is the short version. The full guide, with every step and source, is on GeekSpark.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.