Content Deep Dive

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

Blog post from Cloudflare

Post Details
Company
Date Published
Author
-
Word Count
4,903
Company Posts That Month
17
Language
English
Hacker News Points
-
Post removed?
No
Summary

F5 and nginx.org disclosed ten nginx vulnerabilities on November 18, 2026, including five memory-corruption flaws dubbed “nginx2root” that can crash worker processes and, according to researchers, potentially enable remote code execution; a separate Linux kernel use-after-free could allow an attacker who has compromised a worker to gain host-level root privileges, even from a Docker container. The HTTP/2 and HTTP/3 flaws affect widely used configurations, while the resolver and mail-proxy flaws require more specific settings; nginx releases 1.30.7 and 1.31.9 address the nginx bugs, alongside five other CVEs. Cloudflare says its edge is unaffected and that its HTTP proxy protects origins from the HTTP/2 and HTTP/3 attacks by terminating client connections, but this protection depends on preventing direct access to the origin and does not cover mail traffic, Spectrum TCP/UDP applications, or fully address the resolver flaw. Administrators are urged to update nginx, verify distribution-specific fixes, restrict origin access to Cloudflare, and disable affected features if patching is delayed; blocking the SCTP kernel module is a temporary precaution until a kernel fix is available. As of November 19, no nginx2root CVE was listed in CISA’s Known Exploited Vulnerabilities catalog, and no in-the-wild exploitation had been reported, though the number of potentially exposed servers is substantial.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.