Nginx2Root: Patching nginx This Morning, and Why BareProxy Is Written in Go
nginx2root landed overnight. Five memory corruption bugs in nginx, named and mostly found by Xint, fixed in 1.30.7 and 1.31.9, which came out yesterday. Wiz found the same bugs on its own, which cybersecuritymarket.com covers here.
The lead one, CVE-2026-123007, sits in HTTP/2 flow control and goes back to nginx 1.9.5. That's 2015. A client cancels a request, nginx hands the unsent window back without checking it against the maximum, a counter goes over the edge, and the worker copies far more memory than it should. Xint turned that into running commands on a box that serves nothing but static files over HTTPS. Plain default setup. That's the scary part.
Dane Knecht at Cloudflare had the most useful take of the morning:
nginx2root. The HTTP/2 bug in nginx2root goes back to nginx 1.9.5. The 5 memory corruption bugs in nginx were discovered by Xint. Depending on config, an attacker can cause a DoS with a a crashed worker or trigger RCE and run code.
— Dane Knecht 🦭 (@dok2001) November 19, 2026
It is fixed in Nginx 1.30.7 and patched in 1.31.9.
Cloudflare's edge was fixed globally before disclosure, so proxied traffic locked down to us needs nothing from you. If you are using as for DNS-only or proxy just TCP with spectrum please patch your origin.
https://t.co/YspFQqe10x
What to do about it
Sitting behind Cloudflare's proxy with the origin locked to Cloudflare? The edge already took the hit. DNS-only, Spectrum TCP passthrough, or any box where nginx answers the internet directly: 1.30.7 or 1.31.9, today. If an upgrade has to wait, take http2 off the listen line until it can. You lose a bit of speed and gRPC proxying breaks. Fine for a week.
The full rundown of all five bugs, which configs each one needs and who can skip the patch is on s3h.com: Nginx2Root Opens Every nginx Release Since 2015 to Remote Code Execution.
The BareProxy angle
This is the exact reason BareProxy has a Go core. nginx is brilliant C, and it has been hardened by more eyes than almost anything on the web, and still an integer slip from 2015 turned into memory writes in 2026. In C a bad length means you copy past the end of a buffer. In Go the same mistake hits a bounds check and the request dies with a panic. A crash still isn't great. It beats someone else's shell on your server.
Same thinking on the plugin side. BareProxy plugins are WebAssembly modules written in Rust and run in a sandbox, so a buggy plugin can't reach into the proxy's memory. The small core plus plugins idea is on bareproxy.com. Go won't stop logic bugs, or a dumb config. It does take this whole class of bug off the table, and after this morning that feels like a decent trade.