Critical 9.2
F5 / nginx · NGINX Open Source and NGINX Plus · CVE-2026-123007
nginx2root: nginx web servers with HTTP/2 on could be taken over without a login
nginx, one of the most widely used web servers, has five memory flaws that could let someone on the internet run code on the server without logging in. The lead one, CVE-2026-123007 (named nginx2root by the researchers at Xint), is in HTTP/2 handling and has been in every release since 2015. The others (CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425) need HTTP/2 with a backend, certain proxy settings, HTTP/3 or the mail proxy. F5 scores each 9.2. Running code generally needs a memory protection (ASLR) to be off or defeated, which researchers did in tests. No attacks had been reported as of 18 November.
- Affected
- NGINX Open Source 1.9.5 to 1.31.8 with HTTP/2 enabled (CVE-2026-123007); the other four flaws go back further, as far as 0.5.x for the mail proxy. NGINX Plus 37.x before the fixed builds, and the older R releases up to R36. Linux distributions ship their own nginx builds: The Hacker News reported on 18 November that Ubuntu and Debian listed theirs as vulnerable and had not yet shipped fixed packages. A distribution can fix the flaw without changing the version number nginx reports, so check the full package version against its advisory.
- What to do
- Update to NGINX Open Source 1.31.9 (mainline) or 1.30.7 (stable), which fix all five flaws, or NGINX Plus 37.3.0.1 or 37.0.8.1. NGINX Plus R36 and earlier have no fix listed: move to a 37.x release. On a distribution package, install the patched package as soon as it is published. Then restart nginx fully: a reload leaves the old program running. On managed or shared hosting, ask the host to confirm it has updated. If you cannot update yet, switching HTTP/2 off (http2 off; on 1.25.1 and later, and remove http2 from listen lines) blocks CVE-2026-123007 and CVE-2026-123633 only, and breaks native gRPC; switch HTTP/3 off if you use it, and limit mail proxy listeners to trusted networks. Xint also used a Linux kernel SCTP flaw, not yet fixed, to go from nginx to full control of the host: on servers that do not use SCTP, stop the module loading (install sctp /bin/false in a file under /etc/modprobe.d/).General information summarised from the vendor's advisory at the time of writing, not professional advice. Check the vendor's current advisory before acting.
- Why it’s here
- Critical flaws needing no login in a web server that sits in front of a very large share of websites, including many hosting setups; fixes are out and it is widely covered.
