Nginx NGINX2Root: 9.2-Rated Vulnerabilities — Check and Patch Tonight
On November 18, F5 and nginx.org disclosed ten nginx vulnerabilities at once and shipped fixed releases: stable 1.30.7 and mainline 1.31.9. Five of them, reported by the Xint research team and collectively named NGINX2Ro
On November 18, F5 and nginx.org disclosed ten nginx vulnerabilities at once and shipped fixed releases: stable 1.30.7 and mainline 1.31.9. Five of them, reported by the Xint research team and collectively named NGINX2Root, are rated CVSS 4.0 9.2 by F5.
The main one: an HTTP/2 flaw
CVE-2026-123007 is a memory corruption issue in HTTP/2 flow control that an unauthenticated attacker can trigger remotely. It affects nginx 1.9.5 through 1.31.8 — essentially every release since HTTP/2 was introduced in 2015 — as long as HTTP/2 is enabled. Based on Shodan data, Xint estimates that over 90% of identifiable nginx hosts fall in the affected range.
The other four are CVE-2026-123633 (HTTP/2), CVE-2026-123634 (resolver), CVE-2026-121810 (HTTP/3), and CVE-2026-113425 (mail proxy module), each with different prerequisites.
Two clarifications
First, the nginx flaws themselves yield code execution in the worker process. The "root" in the name comes from a demonstration that chained a separate Linux kernel vulnerability — a different bug that needs its own fix.
Second, as of disclosure, neither the vendor nor CISA reports exploitation in the wild, and none of the five is in the CISA KEV catalog. That said, technical analyses and proofs of concept are already public, so scanning will only grow.
One-minute self-check
Check your version:
nginx -v
Check whether HTTP/2 is exposed:
openssl s_client -connect your-domain:443 -alpn h2
If the output shows ALPN protocol: h2, HTTP/2 is on and you are in scope. Also glance at the nginx error.log for unexpected worker process exited on signal entries.
The fix
Upgrade to 1.30.7 (stable) or 1.31.9 (mainline) and restart nginx — a reload is not enough. If you cannot upgrade right away, disabling HTTP/2 mitigates the two HTTP/2 flaws, but it is not a substitute for upgrading.
Sources: nginx.org security advisories, F5 advisory, Xint NGINX2Root write-up.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.