← gociux.comall insights

Vulnerability alert · 19 Nov 2026

NGINX2Root (CVE-2026-123007): is your nginx exposed and what to do now

, Gociux · 19 Nov 2026 · 6 min read

TL;DR

If your nginx is 1.9.5 through 1.31.8 and has HTTP/2 enabled on a listener the internet can reach, you are exposed to CVE-2026-123007. Fixed releases are 1.30.7 (stable) and 1.31.9 (mainline), plus NGINX Plus 37.3.0.1 and 37.0.8.1, all released on 18 November 2026. Distribution packages (Debian, Ubuntu, RHEL, Alpine) were not yet fixed at release time. Most organisations can't patch today, so turn off HTTP/2 now, which takes a reload, and upgrade when your package arrives.

The five vulnerabilities

F5 rates all five 9.2 under CVSS 4.0 and 8.1 under CVSS 3.1 (Qualys). Each needs a specific feature turned on:

The same releases fix all five. Builds without the HTTP/2 module, and versions before 1.9.5, are not affected by the lead flaw. Branches older than 1.30 get no fix; move to 1.30.7 or 1.31.9, or a vendor package with the backport.

How dangerous is it really?

A working proof of concept is public, published by Rapid7 and tuned for Debian 13 amd64 builds. It is noisy: Upwind reports about 60 GB of traffic to crash a worker and about 128 GB to reach code execution, over one long-lived HTTP/2 connection (Upwind). The research team behind the NGINX2Root name says its own exploit worked over public IPs on AWS, GCP and Azure, and it is withholding the final steps. Qualys warns that the current limits don't protect a specific internet-facing server from a capable attacker.

Code runs as the nginx worker user. Root needs a second bug, and the researchers used one: a Linux kernel SCTP flaw with no CVE and no patch yet, which also worked from nginx inside a Docker container (The Hacker News). If your workers run as root, there is no second step at all.

Exploitation status: no attacks confirmed by F5, Wiz or Rapid7, and not in CISA's KEV catalog as of 18 November. Our CVE lookup shows the live status and exploitation-likelihood score.

Am I affected? Three checks

On the nginx host, check that the build includes HTTP/2 and that the configuration turns it on (Qualys):

nginx -V 2>&1 | grep -o -- '--with-http_v2_module'
sudo nginx -T 2>&1 | sed 's/#.*//' | grep -nE 'listen[[:space:]].*http2|^[[:space:]]*http2[[:space:]]+on[[:space:]]*;'

From outside your network, check whether the server accepts HTTP/2; ALPN protocol: h2 means yes:

openssl s_client -connect HOST:443 -servername HOST -alpn h2 </dev/null 2>&1 | grep -E 'ALPN protocol:|No ALPN negotiated'

Don't trust nginx -v alone: distributions backport fixes without changing the version number, so compare the full package release with your distribution's advisory. If a CDN or layer-7 load balancer terminates HTTP/2 in front of nginx, the risk drops. Still test the nginx port directly, because anything that can reach it bypasses the CDN.

What to do, in order

  1. Turn off HTTP/2 now on internet-facing listeners: set http2 off; and remove http2 from listen lines, then reload. Browsers fall back to HTTP/1.1. This covers CVE-2026-123007 and CVE-2026-123633 only, and it breaks gRPC, so gRPC frontends need the upgrade.
  2. Block the SCTP kernel module where you don't use it (almost everyone): add install sctp /bin/false to a file in /etc/modprobe.d/. This removes the published path to root (Upwind).
  3. Make sure workers don't run as root: check the user directive and ps -o user= -C nginx.
  4. Upgrade and restart. Use 1.30.7 or 1.31.9 from nginx.org, NGINX Plus 37.3.0.1 or 37.0.8.1, or your distribution's fixed package when it ships. A reload keeps the old binary running; you need a full restart or a USR2 binary upgrade.
  5. Find the nginx you didn't install yourself: container images (rebuild and redeploy; running pods keep the old binary), appliances, and products that embed nginx. Check the bundled version and whether HTTP/2 is on.
  6. Watch for crashes: repeated worker crashes (worker process … exited on signal in the error log) and very long-lived HTTP/2 connections moving tens of gigabytes are what an exploit attempt looks like.

Kubernetes: ingress-nginx will never be fixed

For PCI DSS and NIS2, an internet-facing web server with a public exploit is a critical patch with a documented interim mitigation. Record which hosts had HTTP/2 enabled, when you turned it off, and when the fixed build went in. Our stack check emails you if nginx lands in CISA's exploited list, and the radar shows which new CVEs are climbing in exploitation likelihood.

Questions

Which nginx versions fix CVE-2026-123007?

nginx 1.30.7 (stable) and 1.31.9 (mainline), and NGINX Plus 37.3.0.1 and 37.0.8.1, released on 18 November 2026. Distribution packages carry backported fixes under their own release numbers, so check your distribution's advisory.

Does disabling HTTP/2 protect nginx from NGINX2Root?

It blocks CVE-2026-123007 and CVE-2026-123633, the two HTTP/2 flaws, but not the HTTP/3, mail proxy and subrequest flaws fixed in the same release. It also breaks gRPC. Treat it as a stopgap until you upgrade.

Is ingress-nginx affected by CVE-2026-123007?

Yes. The community ingress-nginx controller bundles nginx 1.27.1 with HTTP/2 enabled and was archived in March 2026, so no fix will come. Disable HTTP/2 in its ConfigMap and migrate to a maintained controller.

Not sure where nginx runs in your estate?

We find every nginx, including the ones inside containers and appliances, apply the interim mitigations without breaking gRPC, and track the fix through to closure with evidence your PCI DSS or NIS2 auditor will accept.

Request a quote →

Sources

Developing story, last checked 19 Nov 2026 around 07:30 UTC. Check your distribution's advisory for fixed package versions.