Cybersecurity Research

NGINX2Root: Five Critical nginx Flaws Let Attackers Run Code and Reach the Host Beneath Docker

CrowdStrike · 19 Nov 2026
Key Takeaway Patch every internet-facing nginx server now rather than relying on the large data requirement to protect you.

Researchers have disclosed five critical vulnerabilities in nginx, one of the most widely deployed open-source web servers, under the name NGINX2Root. The flaws let an unauthenticated remote attacker run code on a target host. F5 and the nginx project released patches on the same day, November 18, 2026. The two most severe issues, CVE-2026-123007 and CVE-2026-123633, each score 9.2 on CVSS 4.0.

The headline flaw, CVE-2026-123007, is an integer underflow in nginx's HTTP/2 request handling. HTTP/2 is enabled by default in most production deployments. Specially crafted traffic corrupts memory in the nginx worker process and allows arbitrary command execution with no login or user interaction. The other CVEs depend on common configurations: reverse proxy and resolver settings, HTTP/2 or HTTP/3 with upstream forwarding, and mail proxy mode. Nginx on Windows is not affected.

The severity rises because of the chain. The nginx worker normally runs as an unprivileged account such as www-data or nginx. Researchers showed that a separate flaw in the Linux kernel's SCTP networking subsystem can be reached from the compromised worker to gain root, and then used to escape a Docker container to the underlying host.

A public proof-of-concept exists for CVE-2026-123007. Triggering it needs roughly 128GB of HTTP/2 data, about two minutes over a 10 Gbit/s link. That limits opportunistic mass exploitation today, but not targeted attacks, attacks from inside a network, or future techniques that need less data. The exploit happens in memory, so nothing is written to disk. There are no file hashes, domains or IP addresses to match, so detection depends on spotting unusual behaviour from the nginx process afterwards. CrowdStrike describes how its Falcon platform finds exposed hosts and flags that behaviour.

Why it matters

Any business running nginx, especially in Docker containers or as a reverse proxy, is exposed, and the container boundary can no longer be treated as a safe fallback. Because exploitation happens in memory with no indicators to match, signature-based tools will miss the entry point, so the decision is to patch quickly and monitor for abnormal nginx child processes and behaviour. The 128GB data requirement is a weak comfort for targeted attackers or anyone already inside the network.

What to do

  • Patch nginx on all affected hosts using the fixes F5 and the nginx project released on November 18, 2026.
  • Check whether HTTP/2 is enabled, since it is required for CVE-2026-123007 and CVE-2026-123633.
  • Review nginx configurations for HTTP/3 upstream forwarding, resolver settings and mail proxy mode, which the other three CVEs need.
  • Monitor nginx process trees for post-exploitation behaviour that deviates from normal web server activity.

Summarised by CISO AI from CrowdStrike, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.