Thursday, 19 November 2026

NGINX2Root: the nginx versions to install now, and the stopgap

Five critical nginx flaws can let strangers run code on a web server. Here is how to check yours, what to install and what to do if you can't patch.

Server racks with status lights and a laptop on a pull-out shelf in a dim data center aisle

The short version

  • NGINX2Root is the name Xint gave to five critical nginx flaws, each rated 9.2 and each with a working exploit.
  • The worst bug sits in nginx's HTTP/2 code and lets an attacker with no login run code on the server.
  • Fixed releases are nginx 1.30.7 on the stable branch and 1.31.9 on the mainline branch, both out now.
  • A separate, still unpatched Linux kernel bug in SCTP can turn that foothold into full root control, even from Docker.
Quick read · 1 min

NGINX2Root is a batch of five critical bugs in nginx, the web server behind a large share of the internet. Each scored 9.2 out of 10, and the worst lets an attacker with no login run code on a server through its HTTP/2 support. Researchers also chained it with an unpatched Linux kernel bug to take full root control, even from inside Docker.

The fix is out: nginx 1.30.7 on the stable branch and 1.31.9 on mainline. If you run a website or a self-hosted app, check your version and update now.

  • Can't patch yet? Switch off HTTP/2 for now, knowing gRPC apps may break.
  • Block the SCTP kernel module if you don't use it.
  • BTCPay Server and other bundled apps have their own updates to install.

No attacks had been reported at disclosure, but a public proof-of-concept already exists.

Almost every nginx web server you can find on the internet can be taken over by a stranger who never logs in. That is the warning behind NGINX2Root, a set of five critical flaws in nginx that security firm Xint disclosed on November 18, and the fix is a version upgrade that most server owners have not installed yet.

Nginx is the software sitting in front of a huge slice of the web: it serves pages, balances traffic and passes requests to the apps behind it. Web technology tracker W3Techs counts it on 29.7 percent of sites whose server software it can identify. Xint says that as of November 10, 98.9 percent of hosts showing an identifiable nginx version were affected. If you run a website, a self-hosted app or a home server, this is the week to check it. If you just use websites, the good news is that the work falls on whoever runs them.

01

What is NGINX2Root, in plain English?

NGINX2Root is Xint’s umbrella name for five separate nginx vulnerabilities, all rated 9.2 out of 10 under the CVSS 4.0 scoring system, and Xint says it built a working exploit for every one of them. The name tells you the end goal: get from nginx all the way to “root”, the all-powerful administrator account on a Linux machine.

The five bugs are:

  • CVE-2026-123007: the headline flaw. A math error (an integer underflow) in how nginx tracks HTTP/2 flow control lets an attacker push a counter past its limit, so nginx copies data outside the memory set aside for it. The result is remote code execution with no login needed.
  • CVE-2026-123633: a use-after-free bug, meaning nginx keeps using memory it has already handed back, also in HTTP/2 and also able to lead to code execution.
  • CVE-2026-121810: a use-after-free in HTTP/3 (the newer QUIC-based protocol) that matters when nginx passes traffic upstream with proxy_pass, fastcgi_pass or grpc_pass.
  • CVE-2026-123634: a memory bug in the resolver that only bites setups combining resolver, proxy_pass and the mirror directive with mirror_request_body switched off.
  • CVE-2026-113425: a use-after-free in the mail proxy module, for servers using its proxy and auth_http directives.

Several teams found overlapping pieces at roughly the same time. Researchers at Wiz, Rapid7, Ikotas Labs, Metnir and Xint all independently hit the two HTTP/2 bugs. Ikotas calls its find “NGINX2Shell”, Wiz wrote up two flaws, and Xint documented all five. Some of the teams say they used AI models to hunt for the bugs, and Xint says its automated platform turned up four of its five without a human steering it.

Keyboard and two blurred monitors on an administrator's desk at night
02

Why the Linux kernel bug makes it worse

On its own, the main HTTP/2 flaw only gives an attacker the rights of an nginx worker process, which is normally a locked-down account. The scary part of NGINX2Root is the second step. Xint paired it with a bug in the Linux kernel’s SCTP code (SCTP is a networking protocol mostly used for phone-network signalling) that lets a low-level process grab root.

That kernel bug goes back to Linux 4.15, released in 2018. At disclosure it had no CVE number and no patch, and Xint is holding back most of the details until a fix ships. In Xint’s tests, a hijacked nginx worker got root on the host every time, including when nginx was running inside a Docker container. Because every container on a machine shares one kernel, owning the kernel means owning the host and every other container on it.

Many Linux distributions ship the SCTP module and load it automatically the first time any program opens an SCTP socket. Whether an attacker can actually reach it depends on your kernel, which modules are available and how tightly your containers are restricted.

03

Which nginx versions are affected by NGINX2Root?

Practically all of them. The official nginx advisories list these vulnerable ranges for the five flaws:

  • HTTP/2 flow control (CVE-2026-123007): versions 1.9.5 through 1.31.8, which covers every release since HTTP/2 support arrived in 2015.
  • HTTP/2 use-after-free (CVE-2026-123633): versions 1.19.7 through 1.31.8.
  • HTTP/3 use-after-free (CVE-2026-121810): versions 1.25.0 through 1.31.8.
  • Resolver use-after-free (CVE-2026-123634): versions 0.6.18 through 1.31.8.
  • Mail proxy use-after-free (CVE-2026-113425): every version from the early 0.5 series through 1.31.8.

One oddity worth knowing: the nginx project’s own advisory page labels only the HTTP/2 flow control and mail proxy bugs as “major” and the other three as “medium”, even though F5, the company that maintains nginx, gave all five a 9.2 score. Don’t let the softer label slow you down. The flaws that matter most depend on which features your configuration turns on, and HTTP/2 is on in a very large number of setups.

Home network shelf with a mini PC, a switch and ethernet cables
04

How to fix NGINX2Root: the versions to install

The fix is to upgrade to nginx 1.30.7 if you follow the stable branch, or nginx 1.31.9 if you follow the mainline branch. Both are out now and close all five NGINX2Root flaws. They carry 10 security fixes in total, so they also patch several other bugs announced the same day, including an infinite loop in TLS 1.3 request handling.

  1. Check what you run. On the server, run the command nginx -v. Anything at 1.31.8 or below on mainline, or below 1.30.7 on stable, needs updating.
  2. Update from where you installed it. If you use nginx’s own packages, pull the new release. If your copy came with your Linux distribution, a container image or a hosting control panel, watch for that vendor’s update and apply it as soon as it lands. Xint warns that only a small share of servers get a fix the moment the new version comes out, so don’t assume an automatic update has already happened.
  3. Restart and recheck. Reload nginx after the upgrade and run the version check again to confirm the new number.
  4. Block SCTP if you don’t use it. Until a kernel patch exists, Xint advises blocking the SCTP kernel module on machines that don’t need it, through a module configuration file. That stops it loading in future, but it won’t unload a module that is already running and does nothing if SCTP is built straight into your kernel, so a reboot after the change is the safer path.

Xint says F5 and the big cloud providers, Amazon Web Services, Microsoft Azure and Google Cloud, worked together on the patch before it went public.

Can’t patch tonight? The HTTP/2 stopgap

If you can’t upgrade straight away, the advice from Wiz and Xint is to switch off HTTP/2 in your nginx configuration until you can. That shuts the door on the two worst bugs.

There is a cost. Browsers will quietly fall back to the older HTTP/1.1 protocol, which works fine for most websites, but anything that depends on HTTP/2 will break, including apps that talk to each other through Google’s gRPC framework. Treat it as a short-term fix, not a substitute for the upgrade. The other three flaws need specific features (HTTP/3 with upstream proxying, the mirror setup or the mail proxy), so if you use any of those, read the matching nginx advisory for its own workaround.

05

What NGINX2Root means for home servers and self-hosted apps

You don’t need to be a big company to be exposed. Plenty of home NAS boxes, self-hosted dashboards and small business apps put nginx in front of everything, often inside a ready-made bundle that hides it from view.

BTCPay Server, the self-hosted Bitcoin payment tool, is a good example. It shipped an emergency update on November 18 to pull in the fixed nginx. Its users can install it from the web dashboard under Server Settings, then Maintenance, then Update. Anyone running the Docker version over SSH can run the btcpay-update.sh script from the btcpayserver-docker folder. People running it through Umbrel or Start9 should install the update as soon as those platforms make it available. The project also offered a stopgap that turns off HTTP/2 for Docker users who can’t update right away.

The same logic applies to any self-hosted app: check whether it bundles nginx, then look for the maker’s update rather than waiting for a reminder. If you only visit websites and run nothing yourself, there is nothing for you to install. The fix has to happen on the server side.

06

Is NGINX2Root being exploited yet?

No attacks in the wild had been reported at disclosure, but the researchers say they can’t rule out past use given how old some of the bugs are. The clock is also ticking faster than usual.

Rapid7 published a proof-of-concept exploit for the main HTTP/2 flaw on disclosure day, though its version needs roughly 128 gigabytes of HTTP/2 traffic over a single connection, which is slow and noisy. Wiz has kept its own exploit private but says it got reliable code execution against nginx doing nothing more than serving static files, with no backend app or extra modules. Xint’s chief executive, Brian Pak, said AI-assisted attackers can now rebuild exploits from tiny clues, which is why the company kept details tightly held until the patch shipped. Expect easier exploits to appear soon.

07

Quick answers

What is NGINX2Root?

It is Xint’s name for five critical nginx vulnerabilities disclosed on November 18, the worst of which lets an attacker with no login run code through nginx’s HTTP/2 support.

Which nginx version fixes NGINX2Root?

Version 1.30.7 on the stable branch and version 1.31.9 on the mainline branch fix all five flaws. Anything from 1.31.8 down is vulnerable.

Is turning off HTTP/2 enough?

It blocks the two HTTP/2 bugs for now, but it can break gRPC apps and leaves the other three flaws, so upgrade as soon as you can.

You're reading the quick version.