DEV Community

AikaHub
AikaHub

Posted on Originally published at aikahub.com

NGINX2Root (Nov 2026): five critical NGINX bugs, unauthenticated RCE. Are you affected? Copy-paste checks

If NGINX sits in front of anything you run (a web server, a reverse proxy, Nginx Proxy Manager, or a Docker image that quietly ships it), read this today. On 19 November 2026 Hungary's National Cyber Security Center (NBSZ-NKI) issued an alert about five NGINX vulnerabilities disclosed the day before, collectively nicknamed NGINX2Root.

What's wrong

The headline: an unauthenticated, remote attacker can run code on the server with the privileges of the NGINX worker process. According to the alert, chained with a Linux kernel privilege-escalation bug in the SCTP subsystem, this can become root, and under some conditions a container escape.

CVE Area
CVE-2026-123007 HTTP/2 (data-flow control bug, remote code execution)
CVE-2026-123633 HTTP/2 connections and upstream request handling (use-after-free)
CVE-2026-121810 HTTP/3 / QUIC and upstream request processing (use-after-free)
CVE-2026-123634 DNS resolution and subrequests, in certain proxy configs (use-after-free)
CVE-2026-113425 Mail proxy, in certain auth configs (use-after-free)

The HTTP/2 bug affects official NGINX 1.9.5 through 1.31.8 when HTTP/2 is enabled. That's roughly ten years of releases. The alert does not say the bugs are exploited in the wild yet, and it gives no CVSS scores.

What to do

  1. Upgrade to 1.30.7 (stable) or 1.31.9 (mainline) or newer. Distros may backport the fix without bumping the upstream version number, so check your distro's security advisory, not just nginx -v.
  2. Don't forget containers. If NGINX lives inside a Docker image (Nginx Proxy Manager, your own web app image, anything), pull the patched image and recreate the container. Updating the host does not fix it.
  3. If you can't upgrade right now, temporarily disabling HTTP/2 protects against the two HTTP/2 CVEs, but not the other three. Review HTTP/3 (QUIC), proxies using dynamic DNS resolution (resolver), and the mail proxy if you use them.
  4. Check your logs for unusual outbound connections, unexpected NGINX worker crashes, and odd commands spawned by the web server process.

Copy-paste checks (from the alert)

On the server:

nginx -v 2>&1
nginx -V 2>&1 | grep -- '--with-http_v2_module'
sudo nginx -T 2>&1 | grep -E 'http2|http3|quic'
sudo nginx -T 2>&1 | grep -E 'resolver|proxy_pass|fastcgi_pass|grpc_pass|mirror|mirror_request_body|auth_http|proxy on'
Enter fullscreen mode Exit fullscreen mode

From outside, does your server speak HTTP/2? (replace the domain):

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

Two caveats from the alert: a directive being present doesn't prove you're vulnerable, and its absence doesn't prove you're safe. And if Cloudflare or another proxy sits in front, the external probe measures the proxy, not your origin, so run the checks from the server side too.

Sources

Originally published in Hungarian on AikaHub, a Hungarian homelab & self-hosting community.

Top comments (0)