Cloudflare details nginx2root flaws and how its proxy shields origins

Summary
Cloudflare analyzes five nginx flaws and a Linux SCTP kernel bug, explains which HTTP/2 and HTTP/3 attacks its proxy blocks, and outlines patching and origin-hardening steps. No in-the-wild exploitation had been reported as of November 19.
Key points
- The five nginx2root vulnerabilities affect HTTP/2, HTTP/3, resolver, and mail-proxy configurations; Xint reported potential code execution with the nginx worker’s privileges.
- Xint also found a Linux kernel SCTP use-after-free that could let an attacker with code execution as the nginx worker gain host root; no kernel fix was available as of November 18.
- Cloudflare says its edge is unaffected and its HTTP proxy shields origins from the described HTTP/2 and HTTP/3 attacks by terminating client connections and creating separate origin connections.
- That proxy protection does not fully cover the resolver flaw or mail-proxy traffic, and it does not apply when attackers can reach the origin directly.
- The article recommends updating nginx to 1.30.7 or 1.31.9, or a vendor-fixed build, and restricting origin access; it also provides configuration-specific workarounds.
- Cloudflare tested four flaws with AddressSanitizer against nginx 1.31.8 and 1.31.9; it did not reproduce the HTTP/3 flaw.
- As of November 19, the five nginx CVEs were not in CISA’s Known Exploited Vulnerabilities catalog, and the article reported no known in-the-wild exploitation.
Article Details
- Attack Vectors
- An unauthenticated attacker can send carefully ordered HTTP/2 control frames directly to a vulnerable nginx server to trigger CVE-2026-123007; Xint reports that the flaw can enable command execution.
- CVE-2026-123633 can be triggered over a direct HTTP/2 connection when nginx uses proxy_pass, worker connection slots are scarce, and a partially received HEADERS frame leaves a connection reusable.
- CVE-2026-121810 affects direct HTTP/3 (QUIC) connections to nginx using proxy_pass and can close a connection while a request is in progress.
- CVE-2026-123634 requires a resolver lookup shared by a request and a mirror or SSI subrequest, with proxy_pass configured using variables and a carefully timed request cancellation.
- CVE-2026-113425 affects nginx mail proxy configurations using proxy and auth_http; a client connection reset during login can cause a use-after-free.
- The Linux kernel SCTP send-path use-after-free can reportedly let an attacker who already runs code as the nginx worker gain root on the host, including from an nginx process inside a Docker container.
- Defensive Notes
- Update nginx Open Source to 1.30.7 or 1.31.9, nginx Plus to 37.0.8.1 or 37.3.0.1, or install the applicable distribution fix; restart nginx because a configuration reload does not replace the running binary.
- Ensure origins cannot be reached directly: use Cloudflare Tunnel, restrict inbound HTTP/HTTPS to Cloudflare IP ranges at the IP firewall, or require Authenticated Origin Pulls.
- If patching is delayed, disable unused HTTP/2 or HTTP/3/QUIC features, use fixed upstream groups for proxy_pass, and restrict mail listeners to trusted networks.
- Block the SCTP module if it is not needed, then install the kernel fix and reboot when the distribution provides one; blocking the module does not unload an already-loaded module or disable built-in SCTP.
- Review nginx configurations for HTTP/2, HTTP/3/QUIC, variable-based proxy_pass with SSI or mirror subrequests, and mail proxy auth_http. Consider monitoring worker processes for unexpected execve activity and checking the article's described error-log signals.
- The article reports that, as of November 19, 2026, none of the five nginx2root CVEs was listed in CISA's Known Exploited Vulnerabilities catalog and no in-the-wild exploitation reports had been seen. Xint and Wiz Research had not released their exploits; Rapid7 had published a proof of concept described as suitable only for a freshly started local container.
MITRE ATT&CK
T1068 · Exploitation for Privilege EscalationThe Linux kernel SCTP use-after-free is described as a way for an attacker already running code as the nginx worker to gain root.T1190 · Exploit Public-Facing ApplicationThe article describes unauthenticated exploitation of internet-reachable nginx HTTP/2 and HTTP/3 services; Xint reports that the flaws can enable command execution.T1611 · Escape to HostXint reportedly used the kernel SCTP bug to gain root on the host from an nginx process running inside a Docker container.
CVE
CVE-2026-113425F5 · NGINX Open Source; F5 · NGINX Plusbut SSI and other subrequests can still reach the bug. Bind mail listeners to trusted networks for CVE-2026-113425. Restart so old connections close.CVE-2026-118899F5 · NGINX Open Source; F5 · NGINX Plusbefore the vulnerabilities were published. The same releases fix five other nginx CVEs, including CVE-2026-118899, an infinite loop while reading a request body over TLS 1.3.CVE-2026-121810F5 · NGINX Open Source; F5 · NGINX Plusblocks CVE-2026-123007 and CVE-2026-123633. Removing QUIC listeners and setting http3 off; blocks CVE-2026-121810. Point proxy_pass at fixed upstream groups for CVE-2026-123634. Don't rely on mirror_request_bodyCVE-2026-123007F5 · NGINX Open Source; F5 · NGINX Plusfound 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.CVE-2026-123633F5 · NGINX Open Source; F5 · NGINX Plusand Ikotas Labs for CVE-2026-123007, and Metnir, Wiz Research, and Palo Alto Networks Unit 42 for CVE-2026-123633.CVE-2026-123634F5 · NGINX Open Source; F5 · NGINX PlusCVE-2026-123634 (resolver). This depends on how your configuration builds the proxy_pass target from the request, combined with a carefully timed cancellation of an HTTP request. Passing your traffic through
People
Albert EbbF5's advisory credits him with research on CVE-2026-123633, the nginx HTTP/2 use-after-free.memN0psF5's advisory credits memN0ps of Palo Alto Networks Unit 42 with research on CVE-2026-123633, the nginx HTTP/2 use-after-free.Nir OhfeldF5's advisory credits him, at Wiz Research, with research on CVE-2026-123633, the nginx HTTP/2 use-after-free.
Vendors
Cloudflareworld's web servers, so this is a patch-now event. But if your nginx server is reachable only through Cloudflare's proxy, attackers cannot reach the vulnerable code paths for the most serious of these bugs, givingF5On November 18, 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
Products
Dockeralso 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 andLinux kerneluse 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. OtherNGINXOn November 18, 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 anNGINX PlusFind every nginx server. Include nginx Plus, distribution packages, container images and appliances. Run nginx -V and nginx -T on each and note HTTP/2, HTTP/3/QUIC listeners, proxy_pass with variables plus SSI or
