nginx2root flaws put exposed servers at risk; patching remains essential

src-d21d6698

Five newly disclosed nginx vulnerabilities can let unauthenticated attackers crash a worker and, under certain conditions, execute commands with the worker’s privileges. A separate Linux kernel flaw identified by researchers could potentially turn that access into root privileges on the host, including when nginx runs inside a Docker container.

The vulnerabilities were disclosed by F5 and nginx.org on November 18, 2026, under the name nginx2root. The findings make patching a priority for organizations running nginx as a web server, reverse proxy, cache, load balancer or mail proxy. Cloudflare says its edge systems are not affected and that its HTTP proxy can shield origins from the three nginx flaws involving HTTP/2 and HTTP/3, provided attackers cannot bypass the proxy and connect directly to those origins.

Five nginx flaws affect different configurations

The nginx2root group includes CVE-2026-123007, an integer overflow affecting nginx configurations with HTTP/2 enabled. It has been present since nginx 1.9.5. CVE-2026-123633 is a use-after-free issue involving HTTP/2, proxy_pass to a backend and a worker with few available connection slots; it dates to 1.19.7. CVE-2026-121810 affects HTTP/3 configurations using proxy_pass and has been present since 1.25.0.

The other two bugs are configuration-dependent. CVE-2026-123634 involves nginx’s resolver when proxy_pass uses variables alongside a subrequest, such as mirror or SSI. CVE-2026-113425 affects the mail proxy when proxy and auth_http are configured. In its assessments, F5 rated the vulnerabilities High under CVSS 3.1 and Critical under CVSS 4.0, and noted that code execution requires disabling or bypassing address space layout randomization (ASLR).

The HTTP/2 flaw CVE-2026-123007 is especially notable because HTTP/2 is commonly enabled for TLS deployments and the bug affects a long range of nginx versions. Xint reported testing against servers on AWS, Google Cloud and Microsoft Azure. Its November 10 search found 56.7 million hosts matching nginx; among the 11.94 million that reported a version, 98.9% were in the affected range. Censys counted about 8.8 million services with potentially affected versions and HTTP/2 enabled as of November 19. Version banners are not definitive: Linux distributions may backport fixes without changing the upstream version string.

What Cloudflare’s proxy does—and does not—cover

Cloudflare says its edge is not vulnerable. The company reports that it reviewed the nginx components still used in its modified fork and completed a global update before disclosure. It also says its releases address five other nginx CVEs, including CVE-2026-118899, an infinite-loop issue when reading a request body over TLS 1.3.

For a hostname using Cloudflare’s HTTP proxy, client HTTP/2 and HTTP/3 connections terminate at Cloudflare’s edge. Cloudflare then creates a separate connection to the origin. As a result, client protocol frames used to trigger CVE-2026-123007, CVE-2026-123633 or CVE-2026-121810 are not passed through to the origin nginx process. The protection comes from terminating and re-creating connections, not from a web application firewall rule; Cloudflare says no managed rule is needed for these protocol-level flaws.

This protection depends on keeping the origin out of attackers’ direct reach. Cloudflare recommends using Cloudflare Tunnel, restricting inbound web traffic to its published IP ranges at the network firewall, or requiring Authenticated Origin Pulls using mutual TLS. If an attacker can reach the origin directly, the proxy is not in the traffic path.

The HTTP proxy does not protect nginx mail listeners or traffic carried through Spectrum TCP/UDP applications, which can pass through to the origin. It also does not fully protect against CVE-2026-123634, whose exposure depends on nginx configuration and request handling. DNS-only hostnames and internal or otherwise non-proxied nginx servers likewise require their own remediation.

Patch nginx and assess the kernel exposure

Administrators should inventory nginx deployments across servers, containers, appliances and nginx Plus installations, then compare complete package versions with vendor advisories. The recommended upstream fixes are nginx 1.30.7 or 1.31.9, or a fixed build supplied by the operating-system vendor. The source also lists nginx Plus versions 37.0.8.1 and 37.3.0.1 as fixed; affected R34 through R36 releases have no fixed build listed and should be moved to a fixed 37.x release. Restart nginx or perform a binary upgrade after updating: a configuration reload alone does not replace the running binary.

Where immediate patching is not possible, disabling unused HTTP/2 or HTTP/3 listeners and restricting mail listeners can reduce exposure to the corresponding flaws. Configurations that build proxy_pass targets from variables should be reviewed for CVE-2026-123634. These measures are temporary mitigations, not substitutes for applying fixed packages.

Xint also found a use-after-free in the Linux kernel’s SCTP send path, present since Linux 4.15. The flaw could allow an attacker who already controls an nginx worker to gain root on the host. As of November 18, no kernel fix was available, and Xint was withholding technical details pending a fix. Blocking SCTP module loading may serve as a stopgap where SCTP is not used, but does not remove an already-loaded module or disable SCTP built into the kernel.

As of November 19, none of the five nginx CVEs was listed in CISA’s Known Exploited Vulnerabilities catalog, and no in-the-wild exploitation had been reported. That status does not reduce the need to patch exposed systems, verify origin access controls and track the kernel issue.