Daily Tech Now

Daily News on AI, Big Tech, Linux, Security & Gadgets

NGINX2Root Vulnerabilities Need More Than Turning Off HTTP/2: What Nginx Admins Should Do

The nginx team at F5 shipped nginx 1.30.7 and 1.31.9 on November 18 to fix five remote code execution flaws known as NGINX2Root. The fastest workaround, turning off HTTP/2, blocks only two of them. A sixth bug in the Linux kernel, which turns a break-in into root access, still has no patch. Security firm Xint…

NGINX2Root vulnerabilities in the nginx web server, patched in nginx 1.30.7 and 1.31.9, with an unpatched Linux kernel SCTP bug

The nginx team at F5 shipped nginx 1.30.7 and 1.31.9 on November 18 to fix five remote code execution flaws known as NGINX2Root. The fastest workaround, turning off HTTP/2, blocks only two of them. A sixth bug in the Linux kernel, which turns a break-in into root access, still has no patch.

Security firm Xint named the set and published the NGINX2Root technical write-up. None of the five nginx attacks needs a password, an account or any user action. Xint says it validated the main bug on AWS, Google Cloud and Microsoft Azure. It also posted demos for bare-metal servers.

No attacks in the wild have been reported so far. The CERT-EU security advisory 2026-022, issued the same day, confirms that point. The picture shifted on disclosure day, though. Rapid7 published a working proof-of-concept exploit on GitHub.

What NGINX2Root is

NGINX2Root covers five separate nginx bugs. Each one is an independent way in. According to CERT-EU, each lets an unauthenticated remote attacker run code with the rights of the nginx worker process.

That worker usually runs as a restricted account. To get past that limit, Xint found a sixth flaw in the SCTP code of the Linux kernel. Chained together, the bugs gave Xint root on the host. The chain also worked when nginx ran inside a Docker container, and it reached the host and every container on it.

Which nginx servers are at risk

Each bug needs a specific feature to be switched on. The table uses the version ranges from the official nginx security advisories page and the stopgaps Xint lists.

CVE Part of nginx Needs Vulnerable versions Stopgap
CVE-2026-123007 HTTP/2 flow control HTTP/2 enabled 1.9.5 to 1.31.8 Turn off HTTP/2
CVE-2026-123633 HTTP/2 HTTP/2 plus requests forwarded to a backend 1.19.7 to 1.31.8 Turn off HTTP/2
CVE-2026-121810 HTTP/3 (QUIC) HTTP/3 plus requests forwarded to a backend 1.25.0 to 1.31.8 Turn off HTTP/3 and QUIC listeners
CVE-2026-123634 DNS resolver resolver, a proxy_pass target built from request data, and mirror with mirror_request_body off 0.6.18 to 1.31.8 Use fixed upstream groups, set mirror off
CVE-2026-113425 Mail proxy proxy on plus auth_http for IMAP, POP3 or SMTP 0.5.33 to 1.31.8 Bind mail listeners to loopback or firewall them

The sources disagree on two start versions. Xint lists 1.13.4 as the first release hit by the resolver bug and 0.5.15 for the mail proxy bug. The nginx.org page gives 0.6.18 and 0.5.33. Both sides agree that 1.30.7 and 1.31.9 fix everything.

The HTTP/2 bug is the widest. Wiz says it is exploitable in default setups once HTTP/2 is on. Its researchers ran code on an nginx server that only served static files, with no backend app and no third-party modules.

Xint checked Shodan on November 10. It found 56.7 million hosts identified as nginx. About 11.94 million of them, or 21.1 percent, showed a version number. Of those, 98.9 percent ran a release in the range hit by CVE-2026-123007. Xint stresses that this does not prove those servers are vulnerable, since the attack needs HTTP/2.

What changes for you

Open-source nginx

Upgrade to 1.30.7 (stable) or 1.31.9 (mainline). The nginx 2026 release notes show that the update fixes ten bugs in total. Five are outside NGINX2Root:

  • an infinite loop while reading a request body over TLS 1.3 (CVE-2026-118899)
  • a NULL pointer dereference with PROXY protocol version 2, in mainline 1.31.4 and later only (CVE-2026-120993)
  • a buffer overflow when alias is used with try_files (CVE-2026-125283)
  • an SNI bypass in client certificate checks in the stream module (CVE-2026-120967)
  • weak input checks in the stream ssl_preread module (CVE-2026-123640)

A config reload is not enough. Xint and Sophos both note that a reload does not swap the running program. Restart nginx or use a supported live binary upgrade.

Linux distribution packages and images

The version string can mislead you. Distributions often backport fixes and keep the old number. Xint gives an Ubuntu 22.04 example: the package moved to 1.18.0-6ubuntu14.22, yet nginx still reports 1.18.0.

Patch status varied on day one. Cycode’s NGINX2Root fix tracker listed the official Docker Hub images and Alpine 3.24 as fixed on November 18. Debian, Ubuntu and OpenResty had no fix yet. The retired ingress-nginx controller for Kubernetes has no fix planned.

NGINX Plus customers

F5 fixed the main HTTP/2 bug in NGINX Plus 37.0.8.1 and 37.3.0.1, according to Wiz. Older releases R33 to R36 get no patch, so those customers must move to a fixed 37.x build. CERT-EU lists R34, R35 and R36 among the affected versions.

Sites behind a CDN or proxy

Wiz says CDNs and web firewalls that end the HTTP/2 connection may partly block attacks. Rapid7 adds that its exploit will likely fail through an HTTP/2 proxy. Xint advises testing the origin server directly, not the CDN in front of it.

Steps to take now

  1. Check the version with nginx -v. Run nginx -V to see if the build includes --with-http_v2_module.
  2. Run nginx -T and look for listen ... http2 or http2 on; in your config.
  3. Install the fixed package, then restart nginx.
  4. If you cannot patch yet, turn off HTTP/2. On nginx 1.25.1 and later, set http2 off;. On older releases, remove http2 from the listen line. This breaks native gRPC clients.
  5. For HTTP/3, remove quic listeners, set http3 off and clear the Alt-Svc header. Blocking UDP port 443 is optional.
  6. Fix resolver setups with fixed upstream groups. Bind IMAP, POP3 and SMTP listeners to 127.0.0.1 or limit them with a firewall.
  7. Block the kernel SCTP module on hosts that do not need it. Add install sctp /bin/false to a .conf file under /etc/modprobe.d/. This does not unload a module that is already loaded.

How to look for signs of an attack

Normal access logs will not show this attack. The WINDOW_UPDATE and RST_STREAM frames it uses are not logged as requests, and TLS encrypts them in transit.

Xint suggests a few checks instead. Use ss to find long-lived connections on port 443 from one IP that receive far more data than they send. Many short TLS connections from the same address are another hint. An auditd rule on the worker’s user ID can record programs it starts. A shell such as /bin/sh launched by a worker is the clearest sign of compromise.

Crashes matter too. Search error.log for “signal 11” or “segfault”, and run coredumpctl list nginx. CERT-EU says worker crashes point to possible attempts, not proven code execution. It advises checking process creation logs as well. Each sign can have an innocent cause, so look for several at once.

Technical details: how the HTTP/2 bug works

HTTP/2 lets a client tell the server how much data it may send. The client does this with WINDOW_UPDATE messages. nginx keeps a running count of that allowance.

Rapid7’s CVE-2026-123007 analysis explains the flaw. When a client cancels queued data, nginx hands the reserved credit back without checking the protocol limit. A later check then wraps around, so huge increments pass. In the end, a memory copy gets a giant length and reads and writes outside its buffer.

Xint and CERT-EU call this an integer overflow. Rapid7 and Wiz call it an integer underflow. They describe the same bug.

The exploit first leaks memory addresses to beat address randomization (ASLR). It then overwrites a cleanup function that nginx calls when a connection closes. F5 says code execution requires ASLR to be disabled or bypassed, as Sophos reports. Wiz argues that ASLR does not help, because attackers can read memory first.

Rapid7’s public exploit has real limits. It needs about 128 GB of HTTP/2 traffic over one connection. That takes about two minutes at 10 Gbit/s and about 17 minutes at 1 Gbit/s. Below roughly 300 Mbit/s, nginx’s default one-hour connection limit cuts it off. It also depends on a specific glibc copy routine used on CPUs with AVX-512. Rapid7 says other methods may work, but none are known yet.

The Linux kernel SCTP bug

The kernel flaw sits in the SCTP send path. A waiting send can have its connection moved to another socket and then freed. That leads to a use-after-free or a double free. The bug arrived in Linux 4.15 in 2018.

Xint says it leaks kernel memory, defeats kernel ASLR and allows a kernel function call. Whether an attacker can reach it depends on the kernel, its modules and container limits. The bug has no CVE number and no patch yet. Xint is holding back most details until a fix ships.

How the flaws came to light

An Xint researcher found CVE-2026-123007 while preparing for the ZeroDay Cloud 2026 contest. A few days later, an automated Xint scan found the other four with no human guidance. Wiz, Ikotas Labs, Metnir and Rapid7 also found the HTTP/2 bugs on their own, according to Wiz’s NGINX HTTP/2 advisory. Wiz used its Wiz Atlas tool and checked impact with Gemini 4 Carbon and ChatGPT 5.6 Sol.

  • October 11: Xint finds the bugs (Korea time).
  • October 16: Xint reports them to F5 through HackerOne.
  • October 21: Wiz reports CVE-2026-123633. F5 says another team got there first.
  • November 10: F5 asks Xint to validate the patches. Xint does so that day.
  • November 11 and 12: Rapid7 contacts F5 and sends details of the HTTP/2 bug.
  • November 16: Wiz reports CVE-2026-123007. F5 sets November 18 as the disclosure date.
  • November 18: F5 releases fixes, CERT-EU issues its advisory and Rapid7 posts its exploit.

The pace of nginx bugs has jumped. Xint counts 2 new nginx advisories in 2025 and 26 by November 17, 2026, before NGINX2Root. It credits AI-assisted research for part of that rise. In May, F5 fixed CVE-2026-42945, known as NGINX Rift. Attackers began exploiting it within days, Help Net Security reported.

What remains unclear

The biggest gap is the kernel. Patching nginx does not fix the SCTP bug, and no date for a kernel patch is public.

Severity labels also differ. F5, Wiz and Rapid7 rate the HTTP/2 bugs 9.2 under CVSS 4.0. CERT-EU lists all five at 8.1, the score F5 gives under the older CVSS 3.1 scale, per Precursor Security’s NGINX2Root tracker. The nginx.org page rates CVE-2026-123007 and CVE-2026-113425 “major” and the other three “medium”.

Watch for Debian and Ubuntu packages, a kernel fix and any reports of real attacks. With a public exploit now online, CERT-EU advises patching internet-facing servers first.

About the Author

Trang Nguyen Avatar

Leave a Reply

Your email address will not be published. Required fields are marked *