The worst of the five flaws does not need a password. It needs only HTTP/2 turned on, and that is commonly enabled on TLS deployments. This is CVE-2026-123007, and it has been in every nginx release since 1.9.5, when HTTP/2 support shipped.
Fact
The facts: on 18 November 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx. Five of them, detailed by the Xint research team and published under the name nginx2root, are memory corruption flaws that an unauthenticated attacker can use to crash an nginx worker or, per Xint's research, run commands on the server. Xint also found a Linux kernel bug that turns that foothold into root on the host, including from inside a Docker container. Other teams found the two HTTP/2 bugs independently: F5 also credits Rapid7, Wiz Research and Ikotas Labs for CVE-2026-123007, and Metnir, Wiz Research, and Palo Alto Networks Unit 42 for CVE-2026-123633. The third one in this text is CVE-2026-121810, a use-after-free in HTTP/3 (QUIC) with proxy_pass to a backend. F5 rates each one High (CVSS 3.1: 8.1) and Critical (CVSS 4.0: 9.2), and notes that code execution requires disabling or bypassing ASLR. The fix is nginx 1.30.7 or 1.31.9 (or your vendor's fixed build) and a restart. As of 19 November, none of the five nginx2root CVEs is in CISA's Known Exploited Vulnerabilities catalog, and Cloudflare has not seen reports of exploitation in the wild. Xint searched Shodan on 10 November, before the disclosure, and found 56.7 million hosts matching product:nginx; of the 11.94 million that reported a version, 98.9% fell in the affected range. As of 19 November, Censys's nginx2root exposure tracker counts about 8.8 million services running a potentially affected version with HTTP/2 enabled.
If your nginx is reachable only through Cloudflare's proxy, attackers cannot reach the vulnerable code paths for the most serious of these bugs. Cloudflare terminates every client HTTP/2 and HTTP/3 connection at its edge and opens a separate connection to your origin. The attacker's frames never reach your nginx.
The attack needs billions of frames on one connection. The proxy does not give it that connection.
There is also where the protection stops. The resolver bug is not fully protected and depends on how your config builds proxy_pass. The mail proxy bug is not protected at all, because Cloudflare's HTTP proxy does not carry mail traffic. Both need a specific configuration, but the safest way to be sure is to update.
The sixth part of nginx2root is in the Linux kernel, not in nginx. Xint found a use-after-free in the kernel's SCTP send path, present since Linux 4.15 (2018). As of 18 November, no kernel fix was available and Xint was withholding the details until there is one. The attacker has to already run code as the nginx worker to use it.
Update to 1.30.7 or 1.31.9 and restart. Cloudflare's proxy stops the worst of it, but only while your traffic goes through it. The patch does not apply itself. Today, not on Monday.
Official primary sources
Cloudflare - nginx2root: five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them (CVE-2026-123007, CVE-2026-123633, CVE-2026-121810), 20.11.2026The visual is generated code-art, no third-party images.