Vulnerabilities and exploitation

Public exploits land for NGINX2Root flaws as F5 reports no attacks yet

Working proof-of-concept code for CVE-2026-123007 is now public, and Censys estimates roughly 8.8 million NGINX services are potentially exposed, based on version numbers and HTTP/2 support.

By Junglewise News DeskPublished 6 min read
A tangle of blue network cables plugged into a dark server rack, with small yellow port lights visible.
Photo by Scott Rodgerson on Unsplash

Proof-of-concept exploit code for the most serious of the five NGINX2Root vulnerabilities is now public, and at least one version achieves unauthenticated remote code execution. Rapid7 published a repository containing both a minimal crash trigger and a full exploit for CVE-2026-123007, demonstrated against NGINX 1.31.8 running in a Docker container with HTTP/2 over TLS, according to Tenable. Censys reproduced the flaw's behaviour in its own lab using cleartext HTTP/2 and published a separate proof-of-concept on GitHub.

Despite the exploit code, no attacks have been observed. F5 said it has found no evidence of active exploitation of any of the NGINX2Root vulnerabilities and continues to monitor, with updates on myF5. CERT-EU reported the same, noting that researchers have nonetheless successfully demonstrated use of CVE-2026-123007. Tenable reported that as of 18 November 2026 the five CVEs were not listed on the Known Exploited Vulnerabilities catalogue maintained by the US Cybersecurity and Infrastructure Security Agency (CISA).

The exposure is wide. Censys' live tracker put roughly 8.8 million NGINX services in a potentially exposed state as of 19 November based on version numbers and HTTP/2 support, BleepingComputer reported, with more than 511,000 previously exposed services already patched or mitigated and another 104 million services not disclosing a version at all. Successful exploitation of CVE-2026-123007 gives an attacker code execution with the privileges of the NGINX worker process, on a server that may be doing nothing more exotic than serving static files.

Background

F5 published its advisory on 18 November 2026, fixing five NGINX vulnerabilities that allow unauthenticated remote code execution with NGINX worker privileges, alongside five lower-severity issues and twelve BIG-IP bugs. The name NGINX2Root was coined by Xint (Theori), not by F5 or nginx.org, and covers the five NGINX flaws plus a separate, still-unpatched Linux kernel privilege escalation bug that Xint says can be chained with them to reach root.

The bugs were found independently by researchers at Xint, Wiz, Ikotas Labs, Metnir and Rapid7, using AI-assisted analysis. One of them had been sitting in the code since HTTP/2 support arrived in NGINX 1.9.5 in 2015, which is a long time for a flaw to go unnoticed in software that The Register notes powers about a third of all websites, roughly 225 million of them. Xint said a researcher found CVE-2026-123007 while preparing for ZeroDay Cloud 2026, and added: "A few days later, a fully automated Xint scan found the other four without human guidance."

Not everyone reads the exposure numbers as alarm. Security researcher Florian Roth, commenting on X, said that on exploitability risk "it's worse than Node2Shell and Java2Shell", but that nginx2root does not look like an imminent threat for most deployments because the flaws require non-default configurations. Roth also warned that claims of widespread exposure based on version numbers alone are misleading, and found in a sample of a few hundred NGINX HTTPS endpoints from Shodan that around 66% support HTTP/2.

What to do now

  1. Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline). For NGINX Plus, move to 37.0.8.1 or 37.3.0.1. If you run NGINX Plus R33 to R36, there is no patch for those branches and you need to move to a 37.x release.
  2. Restart NGINX after upgrading. A configuration reload does not replace the running executable, so a reloaded server keeps the vulnerable binary in memory.
  3. Prioritise internet-facing systems, as CERT-EU recommends. Check whether HTTP/2 is enabled on any reachable listener: that is the only precondition for CVE-2026-123007.
  4. If you cannot patch immediately, apply the mitigation that matches the feature you actually use. Disabling HTTP/2 (removing http2 from listen directives or setting http2 off) covers CVE-2026-123007 and CVE-2026-123633 only. Removing QUIC and HTTP/3 listeners covers CVE-2026-121810. Binding mail listeners to loopback or restricting them with a firewall covers CVE-2026-113425. Pointing proxy_pass at a fixed upstream group and turning off mirror where it is not needed covers CVE-2026-123634. Xint cautions that disabling HTTP/2 is not a blanket workaround and that turning off mirror alone does not make a server safe.
  5. Watch the NGINX error log for worker crashes (worker process … exited on signal). CERT-EU describes this as a low-fidelity indicator of exploitation attempts; confirming compromise means checking process creation logs as well.
  6. On hosts that do not use it, block the SCTP kernel module. Xint recommends this until a fix lands for the kernel flaw used in the privilege escalation chain.

Technical details

The five NGINX2Root issues are CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. F5's CVSSv4 scoring rates each at 9.2; CERT-EU lists CVSS 8.1 for all five under the v3.1 scoring, with CVE-2026-123007 carrying the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

CVE-2026-123007 is an integer overflow in HTTP/2 flow control producing an out-of-bounds heap write, tracked under CWE-191 and CWE-787, affecting versions 1.9.5 through 1.31.8. CVE-2026-123633 is a use-after-free (CWE-416) that triggers when connection draining closes an active HTTP/2 connection while NGINX is connecting upstream, affecting 1.19.7 to 1.31.8 and requiring requests to be proxied to a backend. CVE-2026-121810 is the HTTP/3 equivalent (1.25.0 to 1.31.8), CVE-2026-123634 affects DNS resolver waiting list processing (0.6.18 to 1.31.8), and CVE-2026-113425 affects the mail proxy module (0.5.33 to 1.31.8).

Fixed versions are NGINX Open Source 1.30.7 and 1.31.9, and NGINX Plus 37.0.8.1 and 37.3.0.1; CVE-2026-123633 is also fixed in 37.0.7.1 and 37.2.0.1. Amazon Web Services published bulletin 2026-192-AWS on 19 November, saying "These issues have been addressed in nginx version 1.30.7 (stable) and 1.31.9 (mainline)." and that it was actively deploying mitigations worldwide.

Code execution generally requires address space layout randomisation (ASLR) to be absent or defeated. F5 said code execution is only possible if ASLR is disabled or bypassed; Wiz says the two HTTP/2 flaws can themselves bypass it, and Rapid7's exploit recovers heap addresses from server responses. Rapid7's exploit depends on a glibc memory-copy routine specific to x86-64 builds and requires "a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data", which puts exploitation somewhere between two minutes and an hour depending on bandwidth. Where a proxy terminates the HTTP/2 connection, or where the link is slow enough that NGINX's default one-hour connection lifetime expires first, this particular exploit is unlikely to work.

Censys reproduced the memory corruption conditions in four of the five flaws but did not achieve remote code execution. Wiz demonstrated RCE via CVE-2026-123633 and has chosen not to publish that exploit; Xint published demo videos with the final steps intentionally omitted, and is withholding most details of the Linux kernel SCTP use-after-free, which had no CVE assigned as of 18 November.

Xint says it found the bugs on 11 October 2026 and reported them to F5 through HackerOne on 16 October, publishing after the coordinated release on 18 November.

Share this article

On Junglewise Threat Intelligence

The story so far

Related stories

Scan your domain free: see what attackers can see from outside, in about 30 seconds.

This article as Markdown. Atom feed.