nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them
Source
blog.cloudflare.com
Date
Why it matters
Five unauthenticated nginx memory-corruption bugs can lead to code execution, and a chained kernel flaw gives root even from a container. Patch now; origins reachable only through Cloudflare are shielded from the worst of them.
Key takeaways · AI-distilled
CVE-2026-123007, the most exposed nginx2root bug, needs only HTTP/2 enabled and dates to nginx 1.9.5 (2015). A refunded flow-control credit can push the send window past 2^31-1, after which the unsigned overflow check wraps and accepts every later WINDOW_UPDATE.
Cloudflare says origins reachable only through its HTTP proxy are shielded from the HTTP/2 and HTTP/3 bugs because client control frames end at its edge. The resolver and mail-proxy bugs, Spectrum TCP/UDP apps and any directly reachable origin are not fully covered.
The known exploits of CVE-2026-123007 need about 8.6 billion WINDOW_UPDATE frames (roughly 112 GB); Rapid7's run totals about 128 GB. Cloudflare's detection tip: one long-lived HTTP/2 connection receiving tens of gigabytes while nginx sends little back.
Per Cloudflare, http2 off blocks two of the CVEs and removing QUIC/http3 listeners blocks a third. Patching to nginx 1.30.7 or 1.31.9 requires a restart or binary upgrade, because a config reload keeps the vulnerable binary running.
Cloudflare argues an invariant test (the send window never exceeds its protocol maximum) would flag CVE-2026-123007 once a test reached the bad state, which Censys did with a 5.69 MB capture; crash-driven testing needs tens of gigabytes of input.