NGINX2Root: nginx HTTP/2 Flaw CVE-2026-123007 (CVSS 9.2) Allows Unauthenticated RCE in Every Release Since 2015, Public PoC Out and a Kernel Chain to Root — Update to 1.30.7 or 1.31.9

Cyber · 2026-11-19 · By H.A

NGINX2Root: nginx HTTP/2 Flaw CVE-2026-123007 (CVSS 9.2) Allows Unauthenticated RCE in Every Release Since 2015, Public PoC Out and a Kernel Chain to Root — Update to 1.30.7 or 1.31.9

F5 fixed ten nginx flaws on 18 November, including five rated CVSS 9.2 and an HTTP/2 flow-control bug (CVE-2026-123007) that researchers exploited in default setups with ASLR bypassed, and chained with an unpatched Linux SCTP kernel bug to get root.

What Happened

On 18 November 2026, F5 shipped nginx 1.30.7 (stable) and 1.31.9 (mainline). The two releases fix ten vulnerabilities in the open-source web server. Five of them are rated 9.2 under CVSS 4.0 and can lead to remote code execution. The most serious one, CVE-2026-123007, is a memory corruption bug in HTTP/2 flow control. It sits in code that every official release since nginx 1.9.5 (2015) contains, and the researchers say it can be reached in a default HTTP/2 setup with nothing behind nginx but static files.

One of the research teams calls the set "NGINX2Root". At least five groups reported the bugs on their own: an AI security company, a cloud security vendor and three other research teams. The AI company says its automated platform found four of its five reported flaws with no human guidance. It also says it chained the HTTP/2 bug with an unpatched Linux kernel flaw to get root on the host, even from inside a Docker container.

No attacks in the wild had been reported at the time of writing. However, one of the research teams released a proof-of-concept exploit for CVE-2026-123007 on disclosure day. Nginx runs roughly three in ten websites whose server software can be identified, and it is everywhere as a reverse proxy, load balancer and Kubernetes ingress. That makes this the patch to do first this week.

The Two HTTP/2 Bugs

Both HTTP/2 flaws need HTTP/2 to be turned on, and most public nginx servers serving TLS turn it on.

The public proof of concept for CVE-2026-123007 is heavy. According to the researchers, it needs about 128 GB of HTTP/2 traffic over a single connection, and its authors noted that other exploitation methods "may be viable, but none are currently known". That much traffic is a real obstacle, but it is not a defence. A long-lived HTTP/2 connection moving huge amounts of data is exactly the signal defenders should look for.

The Other Critical Flaws

The same releases fix three more bugs rated 9.2 that depend on configuration:

Lower-rated fixes include an infinite loop when reading a request body over TLS 1.3 (CVE-2026-118899, a denial of service), a NULL pointer crash with PROXY protocol v2 (CVE-2026-120993, only in 1.31.4–1.31.8), a buffer overflow when alias is combined with try_files (CVE-2026-125283), an SNI bypass in stream client-certificate checks (CVE-2026-120967) and weak validation in the stream ssl_preread module (CVE-2026-123640).

The Root Escalation

On its own, code execution through CVE-2026-123007 runs with the rights of an nginx worker process, which are normally limited. The AI research company says it chained this with a bug in the Linux kernel's SCTP (Stream Control Transmission Protocol) code that dates back to Linux 4.15 (2018). In its tests, a compromised worker reliably became root on the host, including from inside a container. The kernel bug has no CVE and no patch yet, and the company is holding back details until a fix exists.

Most web servers never use SCTP. Blocking the module from loading takes the escalation path away until a kernel fix arrives. Note that this does not unload a module that is already loaded, and it does not help if SCTP is built into the kernel.

Who Is Affected

What To Do Now

Defensive commands to check versions and apply the stopgaps:

# Show the installed version and whether HTTP/2 is enabled
nginx -v
nginx -T 2>/dev/null | grep -nE 'http2|listen .*ssl'

# Temporary: in each affected server block set
#   http2 off;
# then test and reload
nginx -t && systemctl reload nginx

# Block SCTP from loading (does not unload a module already loaded)
echo "install sctp /bin/false" | sudo tee /etc/modprobe.d/disable-sctp.conf
lsmod | grep -i sctp

Why It Matters

This is one of the biggest web-server patch events in years. One bug, ten years old, sits in the default HTTP/2 path of software that serves a large share of the internet. It also shows a pattern we have reported on several times this month: several teams, some of them using AI systems, found the same flaws within weeks of each other. Once researchers and AI tools can find bugs this fast, attackers will be able to as well. With a public proof of concept already out, the safest course is to treat the time to patch as hours, not weeks.

Sources

REEF SENTINEL