CyberPeople

NGINX2Root: How an Unauthenticated Attacker Gets Root on an Nginx Server

NGINX2Root: Critical Nginx RCE via HTTP/2 (5 Vulnerabilities)

Five critical Nginx RCE vulnerabilities (CVE-2026-123007 etc.) let an unauthenticated attacker run code and reach root. How to check and update.

On November 18, 2026, the Xint research team (Theori's research unit) published a breakdown of five critical Nginx vulnerabilities it grouped under the name NGINX2Root. The main one lets an attacker without any authentication execute arbitrary code on a web server, and chained with a separate Linux kernel vulnerability — gain full control (root) over the host, including escaping containers.

This isn't an exaggeration or a lab scenario: the researchers demonstrated the full attack chain in real AWS, GCP, and Azure cloud environments, attacking the server over its public IP. Worst of all, the key vulnerability lived in Nginx's code for over a decade — since HTTP/2 support arrived in version 1.9.5 back in 2015.

What happened

NGINX2Root is a set of five independent Nginx RCE vulnerabilities and one Linux kernel vulnerability, each with a proven exploit. The common thread: the attacker needs neither credentials nor internal-network access — a reachable web-server port suffices.

CVEWhat it affectsSince versionBlocked by disabling HTTP/2?
CVE-2026-123007HTTP/2 (flow control)1.9.5Yes
CVE-2026-123633HTTP/2 + upstream proxying1.19.7Yes
CVE-2026-123634resolver + proxy_pass + mirror1.13.4No
CVE-2026-121810HTTP/3 + upstream proxying1.25.0No
CVE-2026-113425Mail proxy (proxy on + auth_http)0.5.15No

The most serious is CVE-2026-123007, because it only requires HTTP/2 to be enabled. Wiz researchers confirmed code execution even on a server serving only static content — with no application logic or additional modules.

The vulnerabilities were found on October 11, 2026, reported to F5 via HackerOne on October 16, and fixes were released on November 18. The exploit isn't being published yet — the risk is too high — but at least a crash-trigger and a full RCE PoC have already appeared on GitHub.

How the main vulnerability works

CVE-2026-123007 is an integer underflow in HTTP/2 flow-control handling. The mechanics, simplified:

  1. Queue and refund. When response data enters the output queue, Nginx reserves the connection's send-window "credit." A WINDOW_UPDATE frame replenishes that credit while the data is still queued. If the client cancels the stream, the unsent data is removed and the reserved credit returned — pushing the counter above its maximum.
  2. Invalid window and memory access. The next WINDOW_UPDATE check computes the remaining window capacity using a value that already exceeds the limit. Signed/unsigned interpretation differences produce an incorrect copy length in the TLS output path, leaking memory addresses and corrupting heap metadata.
  3. Worker code execution. The attacker overwrites the connection's cleanup-function pointer with controlled data. When the connection closes, that function runs — executing commands with nginx worker privileges.

In the demonstrated chain, a separate Linux kernel SCTP subsystem vulnerability then escalates from the worker account to root — notably, in Xint's tests the chain escaped a Docker container onto the host. Importantly, the kernel is patched separately from Nginx, and the kernel fix wasn't out yet at publication.

Why this is serious: scale

The numbers from Xint's report speak for themselves:

  • In a November 10 Shodan snapshot, 98.9% of hosts with an identifiable Nginx version ran releases in the vulnerable range — about 11.8M of 11.94M servers.
  • Per W3Techs, Nginx serves roughly a third of the world's websites.
  • 88.6% of Fortune 500 companies use Nginx.

To be fair, these numbers show version prevalence, not a count of guaranteed-vulnerable endpoints. Exploitation requires HTTP/2 enabled, and distribution packages may have backported the fix without changing the version number. Still, the scale of potential impact is unprecedented for a web server of this class.

How to check if you're vulnerable

A server is vulnerable to CVE-2026-123007 if these conditions all hold: unpatched version + HTTP/2 module built + HTTP/2 enabled in config. Check step by step.

Step 1 — server version:

nginx -v 2>&1

If it's an official release from 1.9.5 through 1.31.8, the code is vulnerable. For distribution packages (Ubuntu, Debian) the version number can "lie": check your OS advisory for the fix rather than relying on nginx -v alone.

Step 2 — is the HTTP/2 module built in:

nginx -V 2>&1 | grep -- '--with-http_v2_module'

Empty output means the module is absent and this specific flaw doesn't affect you.

Step 3 — is HTTP/2 enabled in config:

nginx -T 2>&1 | grep -nE 'listen[[:space:]]+.*http2|http2[[:space:]]+on'

A line like listen 443 ssl http2; or http2 on; means HTTP/2 is on.

Step 4 — is HTTP/2 reachable from outside. Run from a machine outside your network:

openssl s_client -connect example.com:443 -servername example.com -alpn h2 </dev/null 2>&1 | grep -E 'ALPN protocol'

If you see ALPN protocol: h2, the server accepts HTTP/2 from the internet and the endpoint is exposed. If a CDN or reverse proxy sits in front, also test direct access to Nginx itself.

Server terminal" alt="Server terminal">

How to update

The main rule: updating the package isn't enough — the process must be restarted. nginx -s reload re-reads the config but doesn't replace the running binary: old code keeps running until Nginx is restarted.

For Ubuntu/Debian the sequence is:

sudo apt-get update
sudo apt-get install --only-upgrade nginx
sudo systemctl restart nginx

For servers where Nginx was installed from the official nginx.org repository — the same, but make sure the package source points to nginx.org, not a stale PPA.

After updating, confirm the fixed version is actually running:

nginx -v

The target is 1.31.9 (mainline) or newer, or your distribution package with the backported fix.

If you can't update right now

For CVE-2026-123007 and CVE-2026-123633 there's a temporary mitigation — disable HTTP/2 on the affected listeners. But remember: this does not close the other three vulnerabilities (resolver, HTTP/3, mail proxy), so it's only an emergency stopgap until the patch is applied.

For Nginx 1.25.1 and newer, add to the server block:

listen 443 ssl;
http2 off;

For older versions (1.9.5–1.25.0), just remove http2 from the listen directive:

listen 443 ssl;

After the change, test the config and restart:

sudo nginx -t
sudo systemctl restart nginx

Note: clients like gRPC require HTTP/2, so after disabling it they may stop working — check your services. Ordinary web traffic will fall back to HTTP/1.1.

Server update" alt="Server update">

What to do next

Updating Nginx closes the "way in," but not the whole chain: the kernel (SCTP) vulnerability is patched separately, with the kernel fix due in the coming weeks. When it ships, update the kernel and reboot servers.

Also run a quick compromise audit: unexpected child processes near nginx workers, repeated worker crashes, unusual network activity. Ordinary access logs won't help here — WINDOW_UPDATE and RST_STREAM frames aren't recorded in them, so check error logs and process-startup records too.

If you suspect server credentials may have leaked, check them via the cyberpeople.tech breach-check tool, and help your team sharpen web-infrastructure defense skills with our cybersecurity learning material.

Conclusion

NGINX2Root is a reminder that even the most-audited software can hide a critical flaw for years. For over a decade, unauthenticated RCE lived in Nginx's HTTP/2 code — a web server serving a third of the internet — and was only found now, partly thanks to automated tools the Xint researchers pointed at ~50,000 lines of code.

The main practical takeaway is simple: check your servers' Nginx version and update to 1.31.9 immediately. And don't forget to restart the process — reload won't save you here. When the kernel patch ships, repeat the update cycle to close the second half of the chain that leads to root.

Stay ahead of threats

Weekly cybersecurity intelligence in your inbox. No spam.

CyberPeople contributor