8.8 Million NGINX Services Still Potentially Exposed to Critical NGINX2Root Vulnerability
What happened?
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.
Key details
- Censys counts 8,823,450 NGINX services running affected versions with HTTP/2 enabled.
- Five memory bugs in NGINX worker processes were disclosed by Xint on 18 November 2026.
- CVE-2026-123007 affects all official releases from 1.9.5 through 1.31.8 and requires only HTTP/2.
- Turning off HTTP/2 blocks only two of the five bugs; HTTP/3, mail proxy, or runtime DNS setups remain exposed.
- Censys reproduced use-after-free bugs for three CVEs but not for CVE-2026-121810, and none of the tests achieved code execution.
- Censys saw no exploitation in the wild as of 18 November and none of the CVEs were in the CISA Known Exploited Vulnerabilities Catalog.
What is affected?
- NGINX Plus versions prior to 37.0.8.1 and 37.3.0.1.
How do I fix or mitigate it?
- Upgrade NGINX Open Source to 1.30.7 or later on stable branch, or 1.31.9 or later on mainline.
- Restart the service after updating; a reload does not replace the running binary.
What should defenders look for?
- A program started by an NGINX worker process is the clearest sign of successful compromise.
- Repeated worker crashes may indicate exploitation attempts.
- Heavy inbound traffic on a single long-lived connection can be a weaker hint.
- Large gaps between received bytes and logged request sizes are a weaker hint.
- Suricata signature 9007015 fired once on vulnerable capture and never on patched capture.
Summarised by SecOraLens from Cyber Security News. Always read the original source before acting. How SecOraLens verifies advisories.
What to do next
Brief your board. Brief your team.
Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.
