nginx2root: Five nginx flaws need patching now

nginx2root vulnerabilities affecting nginx web servers

The nginx2root vulnerabilities target one of the most widely deployed web servers on the Internet. F5 and nginx.org disclosed ten nginx flaws on November 18, 2026. Five, documented by the Xint research team as nginx2root, corrupt memory. Without logging in, an attacker can crash an nginx worker with them or, Xint says, run commands on the machine.

What was disclosed

Each of the five bugs works on its own and each needs a different configuration. F5 rates them High on CVSS 3.1 (8.1) and Critical on CVSS 4.0 (9.2). Code execution requires disabling or bypassing ASLR, address space layout randomization. For CVE-2026-123007, Xint showed how it leaked memory addresses to do that.

Credit for the two HTTP/2 flaws is shared. For CVE-2026-123007, F5 acknowledges Rapid7, Wiz Research and Ikotas Labs. For CVE-2026-123633 it lists Metnir, Palo Alto Networks Unit 42 and Wiz Research.

Of the five, CVE-2026-123007 deserves the most attention. It requires only that HTTP/2 be switched on, a common setting for TLS sites, and every nginx release since 1.9.5, when HTTP/2 support first shipped, contains it. Xint demonstrated the exploit across the public Internet against cloud servers on AWS, GCP and Azure.

How many servers are exposed

Before disclosure, on November 10, Xint queried Shodan and counted 56.7 million hosts running nginx. Only 11.94 million exposed a version number, and 98.9% of those were in the affected range. Censys tallied about 8.8 million services on November 19 that run a possibly affected version with HTTP/2 on. Distributions backport fixes, so a version string alone proves nothing, yet the exposure is wide.

Five more bugs are patched in the same releases. The worst of them, CVE-2026-118899, is a loop that never ends while nginx reads a request body over TLS 1.3. An unauthenticated attacker can stall a worker with it, and it affects nginx 1.13.0 and newer.

The Linux kernel bug behind the root access

Xint also found a kernel flaw that turns the nginx foothold into root. It is a use-after-free in the SCTP send path of Linux, present since version 4.15 in 2018. If a send call is waiting, its SCTP association can be moved to a different socket, and the waiting call may then free it. Someone already running as the nginx worker can exploit this, and Xint did so from nginx inside a Docker container.

Because many distributions load the SCTP module on demand when a program first opens an SCTP socket, hosts that never use SCTP may be exposed anyway. No kernel fix existed on November 18, and Xint is holding back technical details until one ships.

Exploitation status

On November 19, CISA’s Known Exploited Vulnerabilities catalog listed none of the five CVEs, and no attacks in the wild had been reported. Xint and Wiz Research have kept their exploits private. Rapid7 released a proof of concept meant only to show the attack on a freshly started local container. Fake exploits are also circulating on GitHub, so be wary of random downloads.

Does a proxy protect you?

The worst bugs sit in how nginx handles HTTP/2 and HTTP/3. Triggering them takes a carefully ordered stream of protocol frames, sent straight to the nginx process, including billions of WINDOW_UPDATE frames. A proxy that terminates client connections and opens its own connection to the origin, such as Cloudflare’s, consumes those frames instead of forwarding them. Cloudflare says its own edge is not affected.

The condition is that attackers can’t reach the origin directly. Options include a tunnel, a firewall that accepts traffic only from the proxy’s published IP ranges, or mutual TLS. The shield has limits: Spectrum TCP/UDP applications pass traffic through unmodified, the nginx mail proxy carries IMAP, POP3 and SMTP outside the HTTP proxy, and the resolver bug CVE-2026-123634 is only harder to exploit, not blocked.

What to do now

  • Find every nginx server, including nginx Plus, distribution packages, container images and appliances.
  • Upgrade open-source nginx to 1.30.7 or 1.31.9. Upgrade nginx Plus to 37.0.8.1 or 37.3.0.1. Plus R34 through R36 has no fixed build, so those installs must move to a 37.x release.
  • Restart nginx or complete a binary upgrade, because reloading the config leaves the old binary running.
  • Compare the full package version with your distribution’s advisory, since backports can leave the reported version unchanged.
  • If you can’t patch, turn off http2 (nginx 1.25.1 and later) to block CVE-2026-123007 and CVE-2026-123633, and remove QUIC listeners and set http3 off to block CVE-2026-121810.
  • For CVE-2026-113425, limit mail listeners to trusted networks.
  • If you don’t use SCTP, add install sctp /bin/false to a file in /etc/modprobe.d/ as a stopgap. It won’t unload a loaded module.

What happens next

The open item is the kernel fix. Until distributions ship an SCTP update, the modprobe block is the only defense, and Xint’s full details stay private. Once a kernel patch lands, install it and reboot.

Source: Cloudflare Blog

Written by

Saksham Bhargava

Saksham Bhargava runs Alteroid and has been writing about consumer technology for over five years, covering iPhone, Android, Windows, AI tools and gaming. With an MCA and six years of hands-on web development experience, he tests the features he writes about on his own devices and focuses on clear, practical guides that solve real problems. Away from the screen, he enjoys travelling to places most tourists skip.