NGINX2Root: five critical NGINX flaws, led by HTTP/2 bug CVE-2026-123007, fixed in 1.31.9 and 1.30.7
TLDR
- Five critical NGINX flaws are fixed in 1.31.9 and 1.30.7, but Cisco and Veeam list products still awaiting fixes.81718
- No malicious use is reported; Cisco knows proof-of-concept code exists and Censys has published a test for CVE-2026-123007.111417
- Modat counts 14.2 million services on an affected version; it says 0.6 per cent of affected services are fixed.14
Researchers and F5 disclosed five critical vulnerabilities in NGINX on 18 November 2026, and The Hacker News reports that NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable) fix all five.8 Rapid7 says it and F5 disclosed CVE-2026-123007 the same day, and The Register reports that F5 published an out-of-band notification covering 10 CVEs in NGINX Open Source.15 CyberScoop reports that each of the five has a working exploit, and dates the disclosure to Tuesday, while Rapid7, The Register and AlmaLinux date it to 18 November, a Wednesday.1567 The two most severe are the HTTP/2 flaws CVE-2026-123007 and CVE-2026-123633, both scored 9.2 on CVSS 4.0, which Wiz says were independently found by Wiz, Ikotas Labs, Metnir, Rapid7 and Xint.2 The other three, CVE-2026-123634 (resolver), CVE-2026-121810 (HTTP/3) and CVE-2026-113425 (mail proxy), are also scored 9.2 and each is reachable only in a particular setup.8 Wiz describes NGINX as the world's most widely used open-source web server, powering more than 225 million websites.2
CVE-2026-123007 is an integer underflow in NGINX's HTTP/2 handling, per Rapid7,1 and Wiz says the affected code dates back to NGINX 1.9.5 in 2015.2 Rapid7 says a remote, unauthenticated client can exploit it to execute code with the NGINX worker process's permissions.1 Its researcher Stephen Fewer demonstrated this against a linux/amd64 Docker image running NGINX 1.31.8 with http2 on and TLS enabled.1 Rapid7 states the limits precisely: exploitation needs approximately 128 GB of HTTP/2 data; the demonstration took two and a half minutes, while transmitting that volume takes about two minutes on a 10 Gbit/s network and seventeen minutes on 1 Gbit/s; and because of NGINX's default one-hour connection lifetime, a network slower than approximately 300 Mbit/s cannot complete it.1 It adds that a proxied HTTP/2 connection will likely not retransmit the attacker's frames in a way that satisfies the exploit, and that the strategy depends on a specific x86-64 glibc EVEX/YMM memcpy implementation chosen at runtime on CPUs with the avx512f and avx512vl features.1 Rapid7 says other exploitation strategies may be viable, but none are currently known.1 CyberScoop adds that most of the traffic is control frames carrying no actual data.6 The Hacker News says F5 states code execution requires ASLR, a memory protection, to be disabled or bypassed, that Wiz said it bypassed ASLR in tests, and that the proof-of-concept code on GitHub is, by its own notes, suitable only against a freshly started Docker container on the same machine.8
Metnir, which calls CVE-2026-123633 Drainbreak, says it is a use-after-free that lets an unauthenticated client run code on an HTTP/2 reverse proxy in NGINX 1.19.7 to 1.31.8.4 It says its pipeline found the bug on 29 August 2026 and that the exploit run it shows executed native code with ASLR enabled and took about ten minutes, nearly all of it spent defeating ASLR.4 Metnir says it reproduced the use-after-free in OpenResty and crashed the shipped binaries of Kong, Apache APISIX, NGINX Gateway Fabric and community ingress-nginx, all of which enable HTTP/2 by default, and that community ingress-nginx was retired in March 2026 and no longer receives security fixes.4 It is withholding its exploit while patched builds reach distributions.4 Xint, which named the set NGINX2Root, says it chained CVE-2026-123007 with a separate flaw in the Linux kernel's SCTP code to gain root on the host, including out of a Docker container, and demonstrated it against a server over a public AWS IP address.3 Xint says it found CVE-2026-123007 while preparing for ZeroDay Cloud 2026 and that a fully automated scan found the other four a few days later.3 AlmaLinux, citing NGINX's credits, lists Xint.io for four of the five and Albert of Vexera AI for CVE-2026-123633, and also credits Maxim Dounin for CVE-2026-113425; NGINX's own credits therefore differ from the researchers' accounts of who found what.7
On exposure, Xint says a Shodan search on 10 November returned 56.7 million NGINX hosts, 11.94 million of which reported an identifiable version, and 98.9 per cent of those fell in the 1.9.5 to 1.31.8 range affected by CVE-2026-123007.3 Xint and CyberScoop both note this counts reported versions, not confirmed exposure, because it does not show whether HTTP/2 is enabled or a fix has been backported.36 An F5 spokesperson told The Register there was no evidence of active exploitation, and The Hacker News says CISA's Known Exploited Vulnerabilities catalogue did not list the flaw on 18 November.58 Disabling HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633 but not the other three, and F5 told CyberScoop that BIG-IP and F5OS are not vulnerable while its cloud services are still being evaluated.36 Fixes are uneven downstream: AlmaLinux backported them to its supported NGINX streams ahead of Red Hat, but says retired streams, including the AlmaLinux 8 default nginx:1.14, will not be patched, and that backports leave the reported version number unchanged.7 The Hacker News says Ubuntu and Debian had not shipped fixed packages on 18 November and that no fix is listed for NGINX Plus R34 to R36.8 AlmaLinux and The Hacker News both say a reload does not load the patched binary, so NGINX must be restarted, or live-binary-upgraded; a reload is not enough.78
Update, 19 November 2026: Ubuntu and Debian have shipped fixed nginx packages, which The Hacker News and Sysdig reported were not yet available on 18 November.815 Ubuntu's notice USN-9159-1, dated 19 November, lists fixed versions for Ubuntu 26.10, 26.04 LTS, 24.04 LTS and 22.04 LTS, for example 1.24.0-2ubuntu7.20 on 24.04 and 1.18.0-6ubuntu14.23 on 22.04, while fixes for 20.04, 18.04, 16.04 and 14.04 are available only through Ubuntu Pro.9 The notice also covers three NGINX flaws outside the five: CVE-2026-118899 (a TLS denial of service), CVE-2026-120967 (a client certificate verification bypass, affecting only 26.04 and 26.10) and CVE-2026-123640 (an information leak when parsing ClientHello messages, addressed only on 26.04 and 26.10).9 Debian's security tracker lists CVE-2026-123007 as fixed in bookworm (1.22.1-9+deb12u11), trixie (1.26.3-3+deb13u11, via DSA-6642-1) and sid, while forky is still listed as vulnerable.10 CSO Online reports that NGINX Plus R33 to R36 will never receive a fix because those releases have reached end of technical support.16 Sysdig says the Kubernetes ingress-nginx project was archived on 24 March 2026 and its controller image bundles its own NGINX build, so the project will not ship these fixes, and that a container image is fixed only when rebuilt and redeployed.15
CISA's assessment of both HTTP/2 CVEs, as CSO Online reports it, is that neither has been exploited in the wild, and SecurityWeek says F5 mentions no exploitation.1613 Censys said it was not aware of any reported exploitation as of 2pm Pacific on 18 November and found none of the five in CISA's Known Exploited Vulnerabilities catalogue, calling that a point-in-time absence of evidence rather than proof, and Modat reported no attacks as of 19 November.1114 Censys has published a test for CVE-2026-123007 on GitHub: a 5.69 MB cleartext HTTP/2 capture that draws different responses from vulnerable 1.31.8 and patched 1.31.9, without the large traffic volume Rapid7's exploit needs.11 Censys says the test confirms the flow-control accounting error but causes no crash.11 It also reproduced use-after-free conditions in CVE-2026-123633 (a worker crash on the official 1.31.8 image), CVE-2026-123634 (under AddressSanitizer, plus crashes on a custom debug build) and CVE-2026-113425 (a crash on 1.31.8), none leading to code execution, and could not reproduce CVE-2026-121810.11 Censys says it has not verified the Linux kernel flaw or Xint's exploit chain.11 BleepingComputer reports that Wiz is not publicly releasing its proof-of-concept exploits.12 Sysdig wrote on 19 November that there was no public proof of concept at the time of publication and that the kernel bug had no CVE or fix, while SecurityWeek reports that Rapid7 and Censys have published proof-of-concept code.1513
Researchers disagree on how easily the flaws can be used. watchTowr's Yordan Ganchev told CSO Online that exploitation requires the target to be directly exposed with no WAF or CDN terminating HTTP/2, must cope with different builds and configurations, and under load can cause more crashes than code execution.16 Security researcher Florian Roth said the flaws are exploitable in non-default configurations and that exposure claims based only on version numbers are misleading, and BleepingComputer reports that roughly 66 per cent of a sample of a few hundred NGINX HTTPS endpoints he took from Shodan supported HTTP/2.12
On exposure, BleepingComputer reports that Censys's live tracker showed about 8.8 million NGINX services potentially exposed to CVE-2026-123007 on 19 November, based on affected version numbers and HTTP/2 support, with more than 511,000 previously exposed services patched or mitigated and another 104 million not disclosing a version.12 Modat counted 90,138,395 nginx services on 19 November, 84.2 per cent of which report no version.14 Of the services that do, it says 14,189,128 run an affected version, and that 0.6 per cent of affected services are on a fixed release, rising to 4.7 per cent on the two branches that have a fix.14 Modat says 12,549,450 of the affected services, 88 per cent, are on branches 0.5.33 to 1.29, where nginx will ship no fix, and that the three most common affected versions, 1.24.0, 1.18.0 and 1.22.1, are the defaults on Ubuntu 24.04, Ubuntu 22.04 and Debian 12, so some may already be patched through backports.14 It adds that a version is not proof a service can be exploited, since that also depends on configuration such as whether HTTP/2 is enabled.14
Update, 20 November 2026: Cisco has published advisory cisco-sa-nginx-nov-2026-e8jska2s, rated Critical, which gives 16:00 GMT on 20 November as its first publication and covers the NGINX2Root CVEs.17 It lists Identity Services Engine release 3.5 (fixed in 3.5 Patch 5, December 2026), Smart PHY (27.1.0, March 2027), Intersight Virtual Appliance (1.1.9-0, December 2026) and Vulnerability Management, formerly Kenna.VM (1.30.7, November 2026), as affected.17 NX-OS Software is listed as affected with no fixed release shown, while Catalyst SD-WAN Validator, IOS XE, IOS XR and UCS Director are still under investigation.17 Cisco lists Catalyst Center, Catalyst SD-WAN Controller and Manager, Nexus Dashboard, Secure Firewall ASA, FMC and FTD, and UCS Central as not affected.17 It says no workarounds are available, that its PSIRT knows proof-of-concept exploit code is available and is not aware of any malicious use, and that the advisory is an interim version 1.0 to be updated as its investigation continues.17
Veeam's knowledge-base article KB4976, published on 20 November, says Veeam Software Appliance and Veeam Infrastructure Appliance 13.1 include an affected NGINX build with HTTP/2 enabled, that a fixed package is not yet available, and that HTTP/2 cannot be disabled on them because Veeam components depend on it.18 Until the package arrives through Veeam Updater, it tells customers to restrict TCP port 443 on the appliances to trusted networks.18 Veeam says Backup for Salesforce 3.2.1 is affected by CVE-2026-123007 and CVE-2026-123633 and can be protected by installing the operating system vendor's NGINX update once released or removing the http2 parameter from its listen directive, and that its AWS, Google Cloud and Azure plug-in appliances receive Ubuntu's patched 1.18.0-6ubuntu14.23 package through Veeam Updater.18
Cloudflare, in a post dated 20 November, says its own edge is not affected and that, for hostnames proxied through it, client HTTP/2 and HTTP/3 connections end at its edge, so an attacker's frames do not reach the origin's NGINX for CVE-2026-123007, CVE-2026-123633 and CVE-2026-121810.19 It says this holds only if the origin cannot be reached directly, and that the mail proxy flaw is not covered and the resolver flaw, CVE-2026-123634, is not fully covered, depending on how proxy_pass is configured.19 As of 19 November, Cloudflare says it had not seen reports of exploitation in the wild, that Xint and Wiz Research had not released their exploits, that Rapid7 has published a proof of concept it describes as suitable only for a freshly started local container, and that fake exploits are circulating on GitHub.19
Why it matters: vendor appliances that bundle NGINX can stay exposed after the upstream fix, as Cisco's affected-product list is still being updated and Veeam tells customers to restrict access to TCP port 443 until its package ships.1718
Sources
- CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED) (Rapid7)
- Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 (Wiz)
- NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching (Xint)
- CVE-2026-123633 (Drainbreak): NGINX HTTP/2 remote code execution (Metnir)
- AI found more critical bugs in another widely used technology running 225M websites (The Register)
- It's NGINX's turn to cause vulnpocalypse headaches (CyberScoop)
- NGINX2Root: Patched nginx packages released (AlmaLinux OS)
- 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers (The Hacker News)
- USN-9159-1: nginx vulnerabilities (Ubuntu)
- CVE-2026-123007 (Debian Security Tracker)
- nginx2root: A simple test for the HTTP/2 flaw and three use-after-free reproductions (Censys)
- Critical NGINX 'NGINX2Root' bugs let attackers hijack servers (BleepingComputer)
- F5 Patches Critical NGINX2Root Flaws as PoC Exploits Go Public (SecurityWeek)
- NGINX2Root: 14 Million nginx Services Affected, Less Than 1% Fixed (Modat)
- NGINX2Root: Five RCE bugs in NGINX, a Linux kernel path to root, and how to detect exploitation (Sysdig)
- AI unearths 'internet breaker' flaws in Nginx web server (CSO Online)
- Vulnerabilities in nginx Affecting Cisco Products: November 2026 (Cisco)
- KB4976: NGINX2ROOT Impact Statement (Veeam)
- nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them (Cloudflare)