8.8 Million NGINX Services Still Exposed to Flaws

About 8.8 million NGINX services are still running a version exposed to the critical NGINX2Root flaws with HTTP/2 switched on, according to a live tracker from internet-measurement firm Censys, two days after fixes were released. The count shows how slowly even a widely publicised patch reaches the servers that need it.
Censys counts 8,823,450 services running an affected NGINX version and offering HTTP/2. Another 441,489 services that were once exposed have since been patched or have turned HTTP/2 off. Censys tracks more than 331 million NGINX web properties, but about 103.4 million hide their version, so the true figure could be higher or lower, and version numbers are an imperfect guide because distributions often backport a fix without changing the version a server reports.
NGINX2Root is the name researchers at Xint gave to five memory bugs in NGINX disclosed on 18 November 2026. Each one can let an unauthenticated attacker crash an NGINX worker process or run their own code inside it, and each needs a different server setup to trigger. The most serious is CVE-2026-123007, an integer overflow in HTTP/2 flow control that affects every official release from 1.9.5, when HTTP/2 support arrived in 2015, through 1.31.8. F5, which maintains NGINX, rates all five flaws 9.2 out of 10 under CVSS version 4.0.
The five flaws, and what each one needs
CVE-2026-123007 needs only HTTP/2 switched on, which is why it is the one defenders worry about most. CVE-2026-123633 needs HTTP/2 with a backend proxy, CVE-2026-121810 needs HTTP/3 with a backend proxy, CVE-2026-123634 needs runtime DNS lookups combined with subrequests, and CVE-2026-113425 needs the mail proxy with authentication. Turning off HTTP/2 therefore blocks only two of the five; servers with HTTP/3, mail proxy or runtime DNS setups stay open until they are patched.
Xint chained the lead flaw with a separate Linux kernel bug to gain root on the host, including from inside a Docker container. No kernel fix was available when the flaws were disclosed. Censys reproduced the use-after-free bugs for three of the five CVEs in the lab, but none of its tests ended in code execution.
No attacks seen yet, but fake exploits are circulating
As of 19 November, none of the five CVEs was in CISA's Known Exploited Vulnerabilities catalogue and no exploitation in the wild had been reported. Rapid7 has published a proof of concept for CVE-2026-123007 that it says only works in narrow lab conditions, and fake exploits are circulating on GitHub. The scale of exposure is underlined by Xint's check of Shodan data from 10 November: of 56.7 million hosts matching NGINX, only 21.1 percent showed a version, and 98.9 percent of those fell inside the affected range for CVE-2026-123007.
Cloudflare says its proxy shields origins, with limits
Cloudflare, which published its own analysis on 20 November, says its edge is not affected and that origins behind its HTTP proxy are shielded from the HTTP/2 and HTTP/3 attacks, because it terminates every client connection at its edge and opens a separate connection to the origin. But the protection only holds if the origin cannot be reached directly, so Cloudflare recommends its Tunnel service, firewalling to Cloudflare IP ranges, or authenticated origin pulls. The shield also does not cover the resolver flaw, CVE-2026-123634, or the mail proxy flaw, CVE-2026-113425, which travels over mail protocols the HTTP proxy does not carry.
What to do now
Upgrade NGINX Open Source to 1.30.7 on the stable branch or 1.31.9 on mainline, or install the distribution's fixed package, then restart the service, since a reload does not replace the running binary. Note that 1.31.8 is vulnerable while the lower-numbered 1.30.7 is fixed, so version numbers alone can mislead. NGINX Plus users should move to 37.0.8.1 or 37.3.0.1. If patching cannot happen immediately, turn off HTTP/2 and HTTP/3 where possible and keep mail listeners away from untrusted users. Censys has also published a small HTTP/2 test that lets defenders check whether a patch took effect without sending the huge volumes of traffic earlier proofs of concept needed.
Frequently asked questions
How do I know if my server is affected? Check the NGINX version and whether HTTP/2, HTTP/3, the mail proxy or runtime DNS features are enabled, then compare the full package version against the distribution's advisory.
Does turning off HTTP/2 fix it? Only partly. It blocks CVE-2026-123007 and CVE-2026-123633, but the HTTP/3, resolver and mail proxy flaws need their own fixes or mitigations.
Has anyone been hacked through NGINX2Root yet? No exploitation in the wild had been reported as of 19 November, and none of the five CVEs was on CISA's exploited list. A limited proof of concept exists, and fake exploits are circulating, so the absence of attacks so far is not a reason to delay patching.