Security News

Five Critical NGINX Flaws Disclosed, Letting Attackers Take Over Web Servers Without a Login

Infosecurity Magazine · 19 Nov 2026
Key Takeaway Check which NGINX version your websites and any hosting providers run, and upgrade to 1.30.7 or 1.31.9, or disable HTTP/2 in the meantime.

Multiple security research teams have independently disclosed five critical vulnerabilities in NGINX, the open-source web server that powers more than 225 million websites. The flaws could let attackers remotely take control of NGINX-based sites without needing to log in. According to CyberScoop, NGINX handles traffic for roughly a third of all websites, and each of the five flaws has a working exploit.

On November 18, researchers at Wiz, Ikotas Labs, Metnir, Rapid7 and Xint published findings against NGINX 1.31.8, the current release at the time. The five CVEs (CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633 and CVE-2026-123634) all carry a critical rating of 9.2 on the CVSS 4.0 scale. The teams reported differing numbers of flaws: Ikotas Labs highlighted one, which it calls 'NGINX2Shell', Wiz detailed two, and Xint documented all five under the name 'NGINX2Root'. Some teams said they used AI models and worked with OpenAI to find the bugs. According to CyberScoop, Xint found four of the five flaws using an automated testing harness with no human guidance.

Wiz described two of the flaws in detail. CVE-2026-123633 is a use-after-free bug that can corrupt memory, and CVE-2026-123007 is an integer underflow in HTTP/2 flow control. Either could let an unauthenticated attacker run code on a vulnerable server. One affects versions dating back to 2015 and the other back to 2020, and exploitation requires HTTP/2 to be enabled. According to CyberScoop, CVE-2026-123007 is the worst of the five: when a client cancels a request, NGINX hands back unused data credit without checking the protocol limit, and a later calculation wraps into a huge number that causes an out-of-bounds memory copy. CyberScoop says Rapid7 researcher Stephen Fewer built an exploit against NGINX 1.31.8 with HTTP/2 and TLS enabled, and that researchers chained it with a separate Linux kernel flaw to gain root. CyberScoop says the other four flaws affect reverse proxying over HTTP/2 and HTTP/3, the resolver and mirror directives, and mail proxying.

CyberScoop reports practical limits on the attack. It needs about 128 gigabytes of HTTP/2 traffic, and NGINX closes connections after an hour by default, so a network slower than about 300 megabits per second cannot finish in time. The exploit also relies on a specific memory-copy routine in the GNU C Library on certain x86-64 chips. Rapid7 said other exploit methods may exist, but none are known.

Wiz reported the issues to F5, the maintainer of NGINX, which has fixed both in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). CyberScoop says F5 released fixes the same day as disclosure. Xint says the three further flaws it found are also addressed in 1.31.9, though some have configuration-specific mitigations in their advisories. Administrators who cannot upgrade straight away are advised to disable HTTP/2 until patching is possible. According to CyberScoop, F5 said BIG-IP and F5OS are not vulnerable, and its cloud services are still being evaluated.

Xint says it had no evidence of exploitation in the wild at publication, but because some bugs are so old, it says exploitation cannot be ruled out. CyberScoop reports that Xint's Shodan snapshot found 98.9% of 11.94 million version-identifiable NGINX hosts running affected releases, though that counts versions rather than confirmed exposure.

Why it matters

Nearly all version-identifiable NGINX hosts in Xint's snapshot run affected releases, and the flaws need no login, so authentication controls offer no protection. The exploit has real constraints (large traffic volume, specific hardware and library), but other methods may exist and working exploits are public, so patching should not wait for a routine cycle.

What to do

  • Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline) as soon as possible.
  • Disable HTTP/2 on internet-facing NGINX servers that cannot be patched immediately.
  • Review the individual advisories for configuration-specific mitigations covering the resolver, mirror and mail proxy features.
  • Inventory NGINX instances, including reverse proxies and load balancers, to find affected versions.
Also reported by CyberScoop

Summarised by CISO AI from Infosecurity Magazine, with the same story also reported by CyberScoop, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.