8.8 Million NGINX Services Still Potentially Exposed to Critical NGINX2Root Vulnerability

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Around 8.8 million NGINX services may still be open to the NGINX2Root flaws. Censys live tracker counts 8,823,450 services that run an affected version and offer HTTP/2. Another 441,489 services that were once exposed have since been patched or have turned HTTP/2 off.

NGINX2Root is a set of five memory bugs in NGINX that Xint disclosed on 18 November 2026. Each bug sits in an NGINX worker process and needs a specific feature to be switched on. Xint says an unauthenticated remote user can use any of them to run commands as that worker.

The most serious one is CVE-2026-123007. It affects every official release from 1.9.5 through 1.31.8, so the flawed code has existed since HTTP/2 first arrived in 2015. Xint chained it with a separate Linux kernel flaw in the SCTP subsystem to get root, and the chain also broke out of a Docker container.

NGINX2Root Vulnerability

The Censys advisory says each bug needs a different setup. CVE-2026-123007 needs only HTTP/2. CVE-2026-123633 needs HTTP/2 with a backend proxy. CVE-2026-121810 needs HTTP/3 with a backend proxy.

CVE-2026-123634 needs DNS lookups at request time plus subrequests. CVE-2026-113425 needs the mail proxy with auth_http. F5 rates all five 8.1 on CVSS v3.1 and 9.2 on CVSS v4.0.

Turning off HTTP/2 blocks only two of the five bugs. Servers with HTTP/3, mail proxy, or runtime DNS setups stay open until they are patched.

Censys tracks more than 331 million NGINX web properties. About 103.4 million of them hide their version, so they are hard to judge from the outside. The count of 8,823,450 comes from visible versions plus HTTP/2 support, and the real figure could be higher or lower. Distribution builds can also carry a fix without changing the version number.

Xint ran its own check on Shodan data from 10 November. Only 21.1% of 56.7 million NGINX hosts showed a version, and 98.9% of those fell inside the affected range for CVE-2026-123007.

Censys ARC built a small cleartext HTTP/2 test. It showed different results on vulnerable 1.31.8 and patched 1.31.9, with a capture of only 5.69 MB. That lets defenders check their patches without sending the 60 to 119 GiB of traffic that Rapid7 reported for its later crash and code execution steps. The files are in the Censys GitHub repository.

The team also reproduced use-after-free bugs for CVE-2026-123633, CVE-2026-123634 and CVE-2026-113425. It could not reproduce CVE-2026-121810, and none of the tests ended in code execution. The advisory notes that Wiz showed code execution on a plain static-file server, while Rapid7 published a proof of concept for CVE-2026-123007 only. Censys has not verified the kernel flaw or the full root chain.

HTTP/2 control frames are hidden by TLS, so network tools see little unless traffic is decrypted. Censys wrote Suricata rules, and signature 9007015 fired once on the vulnerable capture and never on the patched one. The other rules are experimental.

Server logs help more. Xint calls a program started by an NGINX worker the clearest sign of a successful break-in. Repeated worker crashes, heavy inbound traffic on one long connection, and large gaps between received bytes and logged request sizes are weaker hints. Access logs miss the frames this bug uses.

NGINX Patch

Upgrade NGINX Open Source to 1.30.7 or later on the stable branch, or to 1.31.9 or later on mainline. NGINX Plus users should move to 37.0.8.1 or 37.3.0.1. Version numbers can be misleading here, because 1.31.8 is vulnerable while the lower 1.30.7 is fixed. Restart the service after updating, since a reload does not replace the running binary.

If you cannot patch yet, turn off HTTP/2 or HTTP/3 where possible and keep the mail proxy away from untrusted users. Then check every other setup that matches the list above.

Censys saw no exploitation in the wild as of 18 November, and none of the five CVEs were in the CISA Known Exploited Vulnerabilities Catalog. That only reflects one moment in time. NGINX has been busy this year.

Our earlier coverage of an HTTP/2 flaw in NGINX and the HTTP/2 Bomb denial-of-service exploit shows the same protocol under repeated pressure. Xint also notes the advisory list grew from two entries in 2025 to 26 by mid-November, which it links to AI-assisted bug hunting.

The post 8.8 Million NGINX Services Still Potentially Exposed to Critical NGINX2Root Vulnerability appeared first on Cyber Security News.