techweb24.dev
README.md

NGINX2Root (CVE-2026-123007): Update nginx to 1.30.7 or 1.31.9

NGINX2Root: update nginx to 1.30.7 or 1.31.9 to fix CVE-2026-123007

On 18 November 2026 nginx shipped 1.30.7 (stable) and 1.31.9 (mainline) with ten security fixes. The most serious is CVE-2026-123007, a memory corruption bug in HTTP/2 flow control that researchers at Xint have named NGINX2Root. It affects every nginx release from 1.9.5 to 1.31.8. This guide explains what's affected, how to check your servers, and how to update or switch off HTTP/2 until you can.

Short version: update nginx to 1.30.7 or 1.31.9 (or your distribution's patched package) and restart it. If you can't update today, turn HTTP/2 off on every listener. That blocks CVE-2026-123007 but not the other bugs, so it's only a stopgap.

What is NGINX2Root?

NGINX2Root is the name Xint, the research team at Theori, gave to five nginx vulnerabilities it reported to F5, nginx's owner, in October. The headline bug is CVE-2026-123007 in HTTP/2 flow control.

The nginx changelog describes it as a flow control window overflow that "might allow an attacker to cause a segmentation fault in a worker process, or might have potential other impact." F5's description in NVD goes further: the overflow can corrupt heap memory, and attackers can execute code when ASLR is disabled or can be bypassed. NVD lists a CVSS 4.0 score of 9.2 (critical) and a CVSS 3.1 score of 8.1 (high).

Xint says it turned the bug into unauthenticated remote code execution with nginx worker privileges in its tests. It then chained it with a separate Linux kernel vulnerability in SCTP to get root on the host, and demonstrated the chain on AWS, GCP, Azure and bare metal. The bug has been in nginx since HTTP/2 support arrived in 2015.

Diagram of the NGINX2Root chain: HTTP/2 port, nginx worker, commands as the worker user, then host root through a separate kernel bug

Which nginx versions and setups are affected?

For CVE-2026-123007, nginx.org lists versions 1.9.5 through 1.31.8 as vulnerable and 1.30.7+ and 1.31.9+ as fixed. A server is exposed only when all of these are true:

  • It runs an affected version without a backported fix.
  • nginx was built with the HTTP/2 module (most packages are).
  • A listener has HTTP/2 enabled (http2 on; or listen ... http2).
  • That listener is reachable by an attacker, directly or through something that forwards HTTP/2 to it.

The other Xint findings fixed in the same release each have their own version range:

CVEIssuenginx severityVulnerable
CVE-2026-123007Memory corruption in HTTP/2 flow controlMajor1.9.5 to 1.31.8
CVE-2026-113425Use-after-free in the mail proxy moduleMajor0.5.33 to 1.31.8
CVE-2026-123633Use-after-free in HTTP/2 when worker_connections run outMedium1.19.7 to 1.31.8
CVE-2026-121810Use-after-free in HTTP/3 when worker_connections run outMedium1.25.0 to 1.31.8
CVE-2026-123634Use-after-free in the resolverMedium0.6.18 to 1.31.8

The release also fixes CVE-2026-118899, an endless loop while reading request bodies over TLS that nginx rates major, plus issues in the stream module, PROXY protocol v2, ssl_preread and alias with try_files. One update covers all ten.

How do I check if my nginx is vulnerable?

Run these on each server. They show the version, whether HTTP/2 or HTTP/3 is switched on anywhere in the loaded configuration, and whether the site actually negotiates HTTP/2 from outside.

# 1. Version (1.9.5 - 1.31.8 is affected unless your vendor backported the fix)
nginx -v

# 2. Is HTTP/2 (or HTTP/3) enabled anywhere in the running configuration?
sudo nginx -T 2>/dev/null | grep -nE 'http2|quic'

# 3. Does the site negotiate HTTP/2? Run this from outside your network.
openssl s_client -connect example.com:443 -servername example.com -alpn h2 </dev/null 2>&1 | grep ALPN
Terminal output showing an affected nginx version with HTTP/2 enabled and negotiated

If the third command prints ALPN protocol: h2, the endpoint speaks HTTP/2. Check that the TLS connection itself succeeded: a missing line only means something if the handshake worked.

Old version numbers can still be patched. Debian, Ubuntu, Red Hat and appliance vendors often backport fixes without changing the upstream version. Check your vendor's advisory or package changelog for CVE-2026-123007 rather than relying on nginx -v alone. Products that embed nginx, such as ingress controllers and load balancers, need their vendor's update.

How do I update nginx to 1.30.7 or 1.31.9?

Install the fixed release from wherever your nginx comes from, then restart it. nginx -s reload re-reads the configuration but keeps the old binary running, so a reload alone does not apply the fix.

# Ubuntu / Debian (nginx.org repository or distribution packages)
sudo apt update && sudo apt install --only-upgrade nginx

# RHEL, Rocky, AlmaLinux
sudo dnf upgrade nginx

# Test the config, restart, and confirm the running version
sudo nginx -t && sudo systemctl restart nginx
nginx -v

For Docker, update the image tag to nginx:1.30.7 or nginx:1.31.9 (both are on Docker Hub), rebuild anything that uses nginx as a base image, and redeploy. In Kubernetes, ingress controllers built on nginx get fixed through the controller's own release, not by updating nginx yourself.

Can't update yet? Turn off HTTP/2

Disabling HTTP/2 removes the code path CVE-2026-123007 needs. Browsers fall back to HTTP/1.1, so sites keep working, just without HTTP/2 multiplexing.

# nginx 1.25.1 and later: switch the directive off in each server block
server {
    listen 443 ssl;
    http2 off;
    # ...
}

# nginx 1.9.5 to 1.25.0: remove "http2" from the listen line
#   before:  listen 443 ssl http2;
#   after:   listen 443 ssl;

Turn it off in every server block that listens on the same address and port, not just one. Then run sudo nginx -t && sudo systemctl reload nginx and repeat the outside openssl check: it should no longer print ALPN protocol: h2.

This does not protect against the HTTP/3, resolver, mail proxy or TLS body-reading bugs in the same release. If you use listen ... quic for HTTP/3, the HTTP/3 use-after-free (CVE-2026-121810) still applies until you update.

What about the Linux kernel part of the chain?

The step from the nginx worker to root uses a separate Linux kernel vulnerability in SCTP, the networking protocol module. Xint's site does not name that bug's CVE. Updating nginx breaks the chain at the first step, but keep your kernel current too: install your distribution's latest kernel and reboot into it.

Most web servers never use SCTP. If yours doesn't, a common hardening step is to stop the module from loading at all:

# Prevent the SCTP kernel module from loading (only if nothing on the host uses SCTP)
echo "install sctp /bin/true" | sudo tee /etc/modprobe.d/disable-sctp.conf
lsmod | grep sctp    # no output means it isn't loaded now

FAQ

Is NGINX2Root being exploited?

As of 19 November 2026, none of the five NGINX2Root CVEs are in CISA's Known Exploited Vulnerabilities catalog. Xint has demonstrated working exploits, though, and nginx runs a large share of the web, so treat this as urgent.

Does Cloudflare or another CDN protect my origin?

Only partly. A CDN terminates the visitor's HTTP/2 connection itself, but your origin is still exposed if it can be reached directly or if the CDN talks HTTP/2 to it. Lock the origin to your CDN's IP ranges and update nginx anyway.

I run Apache or PHP, not nginx. Am I affected?

Not by NGINX2Root. If you run PHP, though, PHP released its own security updates the next day; see our guide to the PHP November 2026 security release.

Sources: nginx security advisories, nginx CHANGES, NVD: CVE-2026-123007, Xint: NGINX2Root.

Zubaer Ahammed

Full-stack & Android developer from Bangladesh. Builds web platforms and apps and writes practical tutorials here. zubaer.com

Comments