News

nginx2root: five critical nginx flaws, Cloudflare protects origin but patching required

F5 and nginx.org reveal five unauthenticated RCEs in nginx (nginx2root). Fixes in 1.30.7 and 1.31.9, deploy immediately.

UptimeMag editorial team · 20 November 2026 · 2 min read

nginx2root: cinque falle critiche in nginx, Cloudflare protegge l'origin ma va patchato

On 18 November 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx. Five, grouped by research team Xint under the name nginx2root, are memory corruption bugs that an attacker without credentials can exploit to crash an nginx worker, or in some cases execute arbitrary commands on the server. Xint also discovered a kernel Linux bug that escalates that access to root on the host, even from within a Docker container. Anyone running VPS, shared hosting or reverse proxies based on nginx should treat this as a critical patching event.

The five CVEs

On the official security advisory page, nginx.org classifies the flaws as follows—all patched from version 1.31.9 (mainline) or 1.30.7 (stable) onwards:

CVE Component Severity (nginx.org) Vulnerable versions
CVE-2026-123007 HTTP/2 flow control major 1.9.5 – 1.31.8
CVE-2026-123633 HTTP/2 (use-after-free) medium 1.19.7 – 1.31.8
CVE-2026-121810 HTTP/3 (use-after-free) medium 1.25.0 – 1.31.8
CVE-2026-123634 resolver (use-after-free) medium 0.6.18 – 1.31.8
CVE-2026-113425 mail proxy (use-after-free) major 0.5.33 – 1.31.8

The most exposed is CVE-2026-123007: HTTP/2 simply needs to be enabled, a standard configuration on nearly all TLS-enabled deployments. Lab analysis confirms that exploitation requires a direct connection to nginx without an upstream proxy managing HTTP/2 on its own, approximately 119 GiB of traffic within nginx's one-hour connection limit, an idle server, and an x86-64 server CPU with AVX-512. In the same lab, a per-IP connection limit (limit_conn) of 4 or 8 blocked the exploit, which opens 16 extra connections from a single address, but this is merely a mitigation, not a proper patch.

What changes for Cloudflare users

Those running nginx behind Cloudflare's proxy are protected against HTTP/2 and HTTP/3 attacks, because client connections terminate at the edge and traffic to the origin is rebuilt by Cloudflare itself. However, protection does not cover the resolver (which depends on proxy_pass configuration) or mail proxy, which Cloudflare does not route. It applies only if the origin is not directly reachable: verify that ports 80/443 and UDP 443 do not respond from the Internet outside the proxy by using Tunnel, Cloudflare IP allowlist, or Authenticated Origin Pulls.

What to do immediately

Update to nginx 1.30.7 or 1.31.9, or the package provided by your supplier, and restart the process (a reload does not replace the running binary). For NGINX Plus, builds 37.0.8.1 (LTS) or 37.3.0.1 (continuous release) are required. The Linux kernel bug related to SCTP, which Xint used to escalate to root from within a container, had no patch as of 19 November: until one arrives, it is worth verifying whether the SCTP module is loaded unnecessarily and, if possible, disabling it.

Written with the help of artificial intelligence and checked by the editors (EU AI Act, art. 50).