security —

nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them

On November 18, 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx.

nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them

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. 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, giving you protection while you update your servers.

Here is where Cloudflare stands, what that protection covers, where it stops, and how the bugs work. The short version - Cloudflare's edge is not affected. Much of the proxy that handles customer traffic at our edge now runs on FL2, written in Rust. We reviewed the parts still built on our heavily modified nginx fork against all five bugs before disclosure, and an update closing the related code paths finished rolling out globally before the vulnerabilities were published.

Earlier coverage

Reported by blog.cloudflare.com.

securitycloud

Related coverage

Elsewhere in this edition