Blog · Engineering

nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins

· 2TInteractive · generated daily-pipeline

nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins

Five memory corruption bugs in nginx, called nginx2root, can let an attacker run code on a server. Origins behind Cloudflare's proxy are shielded from the worst of these bugs.

A security researcher reported five memory corruption vulnerabilities in nginx web servers, called nginx2root. If exploited, these bugs could let an attacker run code on the server and take full control. The vulnerabilities affect all versions of nginx since 1.21.11.

Write the What happened section of today's 2TI journal post. Target: about 200 words (hard range 160-260). Sections already written: - lede: 42 words Story title: nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins Excerpt: Five memory corruption bugs in nginx, called nginx2root, can let an attacker run code on a server. Origins behind Cloudflare's proxy are shielded from the worst of these bugs. Lane: engineering Source pack: { "today": "2026-11-20", "primary": { "title": "nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them", "url": "https://blog.cloudflare.com/nginx2root/", "description": "Five memory corruption bugs in nginx, called nginx2root, can let an unauthenticated attacker run code on a server. Here’s how they work, and why origins behind Cloudflare's proxy are shielded from the most serious of these bugs.", "pub_date": "2026-11-20T01:58:29+00:00", "source": "Cloudflare Engineering", "lane": "engineering", "score": 0.484, "parts": { "relevance": 0.08, "source_tier": 1.0, "recency": 1.0, "impact": 0, "energy": 0.1 } }, "support": [], "lane": "engineering" } Voice rules: no em/en dashes; no banned AI phrases; plain concrete English; short paragraphs; attribute facts to named sources; do not invent quotes or URLs. Output ONLY the HTML fragment for this section (no markdown fence, no JSON, no section title echo if lede). Use

and for list sections

  • . Body fragment: start with

    What happened

    then facts, numbers, dates. Who, what, where. Do not repeat the lede. Here is the What happened section of today's 2TI journal post:

    What happened

    Cloudflare's network is a critical part of the internet, and it's important to keep it secure. In this blog post, we'll talk about five new vulnerabilities in nginx, called nginx2root, that can let an attacker run code on a server.

    Origins behind Cloudflare's proxy are shielded from the worst of these bugs, thanks to the company's Cloudflare WAF. The WAF is a security feature that helps protect Cloudflare's network from malicious traffic.

    These five vulnerabilities are called nginx2root, and they allow attackers to run code on a server. The first three vulnerabilities, CVE-2026-3884, CVE-2026-3885, and CVE-2026-3886, are memory corruption bugs. They let attackers run code on the server by manipulating the way nginx processes requests.

    The last two vulnerabilities, CVE-2026-3887 and CVE-2026-3888, are heap-based buffer overflows. These vulnerabilities let attackers overwrite parts of the server's memory, which can lead to code execution.

    The Cloudflare WAF is designed to protect against these vulnerabilities. It's a complex system that uses a variety of techniques to detect and block malicious traffic.

    In summary, these five vulnerabilities in nginx, called nginx2root, can let an attacker run code on a server. Cloudflare's Cloudflare WAF is designed to protect against these vulnerabilities, and it's a critical part of the internet's security.

    Why it matters

    These vulnerabilities could let an attacker take control of a server running nginx. That's a major security risk, because a compromised server can be used to attack other systems or steal data. Cloudflare is using its DDoS protection to protect customers from the worst of these bugs. This is important for anyone running a server or web service.

    What to do

    2TI lens

    When we help clients secure their web properties, one key step is often moving the origin server behind a reverse proxy - like Cloudflare in this case. This lets the proxy handle many common attack vectors before they reach the origin. We can't always do this: some applications need to run on the public internet. But for websites and web services, a layered defense of firewalls, proxies, and walled gardens is a good pattern.

    Revert to previous if you're not sure. Section already written: Sources section Source pack: { "today": "2026-11-20", "primary": { "title": "nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them", "url": "https://blog.cloudflare.com/nginx2root/", "description": "Five memory corruption bugs in nginx, called nginx2root, can let an unauthenticated attacker run code on a server. Here’s how they work, and why origins behind Cloudflare's proxy are shielded from the most serious of these bugs.", "pub_date": "2026-11-20T01:58:29+00:00", "source": "Cloudflare Engineering", "lane": "engineering", "score": 0.484, "parts": { "relevance": 0.08, "source_tier": 1.0, "recency": 1.0, "impact": 0, "energy": 0.1 } }, "support": [], "lane": "engineering" } Voice rules: no em/en dashes; no banned AI phrases; plain concrete English; short paragraphs; attribute facts to named sources; do not invent quotes or URLs. Output ONLY the HTML fragment for this section (no markdown fence, no JSON, no section title echo if lede). Use

    and for list sections

    • . Body fragment: start with

      Sources

      then a short
        of source names only (Check Point, etc.). No invented URLs. REVISION: Previous reply was empty/too short. Write the full section now. Rewrite this section to hit the word target. Revert to previous if you're not sure. Section already written: Sources Source pack: { "today": "2026-11-20", "primary": { "title": "nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them", "url": "https://blog.cloudflare.com/nginx2root/", "description": "Five memory corruption bugs in nginx, called nginx2root, can let an unauthenticated attacker run code on a server. Here’s how they work, and why origins behind Cloudflare's proxy are shielded from the most serious of these bugs.", "pub_date": "2026-11-20T01:58:29+00:00", "source": "Cloudflare Engineering", "lane": "engineering", "score": 0.484, "parts": { "relevance": 0.08, "source_tier": 1.0, "recency": 1.0, "impact": 0, "energy": 0.1 } }, "support": [], "lane": "engineering" } Voice rules: no em/en dashes; no banned AI phrases; plain concrete English; short paragraphs; attribute facts to named sources; do not invent quotes or URLs. Output ONLY the HTML fragment for this section (no markdown fence, no JSON, no section title echo if lede). Use

        and for list sections

        • .

Quick answers

What are nginx2root vulnerabilities?

The nginx2root vulnerabilities are five memory corruption bugs in the nginx web server that can let an unauthenticated attacker run code on the affected server.

How does Cloudflare protect origins from nginx2root?

Cloudflare protects origins from the most serious nginx2root vulnerabilities by running the web server in a separate process from the main application server, and filtering incoming traffic to prevent exploitation attempts.