Your dependency scanner cannot see NGINX2Shell. I built a 3-condition check that can.
Your dependency scanner cannot see NGINX2Shell. I built a 3-condition check that can. On 18 November 2026, Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint disclosed NGINX2Shell: two unauthenticated RCE flaws in NGIN
Your dependency scanner cannot see NGINX2Shell. I built a 3-condition check that can.
On 18 November 2026, Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint disclosed NGINX2Shell: two unauthenticated RCE flaws in NGINX HTTP/2. CVE-2026-123007 is an HTTP/2 send_window integer underflow (versions 1.9.5-1.31.8, in the code since 2015). CVE-2026-123633 is an HTTP/2 use-after-free (versions 1.19.7-1.31.8, needs a proxy block and low free worker connections). Both score CVSS 4.0 9.2 Critical / CVSS 3.1 8.1 High. Fixed builds shipped the same day: 1.30.7 stable and 1.31.9 mainline. Wiz demonstrated unauthenticated RCE with an ASLR bypass on official 1.31.7/1.31.8 builds serving ordinary static files over HTTPS, no backend, no third-party module. As of 19 November 2026 there are no reports of exploitation in the wild and neither CVE is in the CISA KEV catalog. Wiz has not published its exploit code; Rapid7 has published a PoC for CVE-2026-123007 (about 128 GB of HTTP/2 traffic over one connection, relying on a specific glibc memory-copy routine chosen on AVX-512 CPUs). Fake nginx2root exploits are already circulating on GitHub - do not run exploit code from untrusted repositories.
Here is the part that should worry every team running NGINX in production: the flaw is in the proxy, not in the app. Clean app code does not help, and a version-only CVE match calls a host "vulnerable" even when its HTTP/2 is off (HTTP/2 defaults to off, and the module is not built by default). Exposure needs the version and the config together, on the host NGINX actually runs on:
- An affected version (CVE-2026-123007: 1.9.5-1.31.8; CVE-2026-123633: 1.19.7-1.31.8).
- HTTP/2 enabled in at least one server block (
listen ... http2orhttp2 on;). - For CVE-2026-123633, the block also proxies to a backend while free worker connections run low.
I built nginx2shell to answer one question per install: do the conditions line up here? It is a zero-dependency TypeScript CLI (Node 20+). Everything runs locally; no network, no CVE database, no exploit code, and it never probes a port or runs exploit input.
What it does
nginx2shell scan [--dirs <dir>...] [--config <file-or-dir>] [--internet-facing] [--sockets <file>] [--json]
nginx2shell check <nginx-dir-or-binary> [--config <file-or-dir>] [--internet-facing] [--sockets <file>] [--json]
nginx2shell config-scan <config-file-or-dir> [--json]
nginx2shell playbook [--json]
nginx2shell explain <topic>
nginx2shell init
-
scandiscovers NGINX installs (fromPATH, well-known dirs, or--dirs) and verdicts each one: EXPOSED, AT-RISK, SAFE or UNKNOWN, with the deciding condition printed per install. -
checkverdicts one install in detail: version, patch range, HTTP/2 state per server block and its config source. -
config-scanreports per-block HTTP/2, proxy, HTTP/3, resolver and mail state from a config file or annginx -Tdump, so you can see exactly which block is the problem. -
playbookprints the first-hour response plan for this disclosure: patch order, thehttp2 off;stopgap, and restart-not-reload (a reload does not swap the vulnerable binary). -
explainprints the CVE facts, the verdict rules and the sources, with the date they were checked (19 November 2026). -
initwrites annginx2shell.config.jsonfor CI use.
Exit codes: scan exits 0 when nothing is EXPOSED, 1 when at least one install is EXPOSED, 2 when no NGINX is found. check exits 0 SAFE, 1 EXPOSED or AT-RISK, 2 UNKNOWN. Both are built to be CI gates: fail the build while any install in the fleet is EXPOSED.
Install from source only - the nginx2shell package is not published to npm yet (the name was unclaimed; npm returned 404 when checked on 19 November 2026):
git clone https://github.com/techdevfun/nginx2shell.git
cd nginx2shell
npm install
npm run build
node dist/cli.js --help
Example output (real CLI output from the demo transcript, demo/transcript.txt; the fleet is synthetic, the 1.24.0 version string is recorded from a real Ubuntu NGINX binary run during the build):
$ nginx2shell scan --dirs nginx-1318 nginx-1307 nginx-1240
install | version | line | http2 | proxy | verdict
/tmp/nginx2shell-demo/fleet/nginx-1318 | 1.31.8 | mainline | on (1 block) | 1 | EXPOSED
/tmp/nginx2shell-demo/fleet/nginx-1307 | 1.30.7 | stable | on (1 block) | 1 | SAFE
/tmp/nginx2shell-demo/fleet/nginx-1240 | 1.24.0 | stable | off (0 blocks) | 1 | SAFE
deciding: affected version + HTTP/2 on (/tmp/nginx2shell-demo/fleet/nginx-1318)
- 1.31.8 is in the affected range for CVE-2026-123007 (fixed build is 1.31.9)
- HTTP/2 is on in at least one server block
- CVE-2026-123633 also applies: an HTTP/2 block proxies to a backend (low free worker connections is runtime state)
deciding: fixed build (/tmp/nginx2shell-demo/fleet/nginx-1307)
- 1.30.7 is at or above the fixed build (1.30.7 stable) for the 18/11/2026 release
deciding: HTTP/2 off, no secondary signal (/tmp/nginx2shell-demo/fleet/nginx-1240)
- 1.24.0 is in the affected range, but HTTP/2 is off in every server block (checked from nginx -T)
- no secondary signal applies (no HTTP/3 listener, no resolver directive, no mail proxy block)
summary: 3 installs scanned - EXPOSED 1, AT-RISK 0, SAFE 2, UNKNOWN 0
Exposure conditions only. This tool does not prove exploitability, never probes a port, and never runs exploit input. A SAFE verdict means these conditions do not line up - not that the host is safe from every NGINX flaw.
exit: 1
The wedge works as designed on a real NGINX, not just fixtures. During the build I downloaded and ran a real Ubuntu NGINX 1.24.0 binary and recorded its nginx -V and nginx -T output as fixtures. The live check on that binary with its real config dump verdicts EXPOSED, exit 1. The same binary with no config readable verdicts AT-RISK honestly, never SAFE. That is the whole point: version alone is the wrong question, and a config you cannot read is not a clean bill of health.
How it compares
| Tool | What it checks | Live HTTP/2 per block? | Local, no network? | Fleet scan + CI gate? |
|---|---|---|---|---|
| Trivy / Grype | Version match against a CVE database | No | No (needs DB) | Yes, for dependencies |
| Wiz / cloud inventory | Fleet version inventory | No (version only) | No | Yes, fleet-wide |
| Nuclei templates | Remote target over the network | N/A (remote probe) | No | Yes, remote scan |
| nginx2shell | Version + HTTP/2 per block + exposure, per install | Yes, from nginx -T
|
Yes | Yes, exit codes + --json
|
No dedicated Nuclei template for these CVEs was found by search on 19 November 2026, and the version-only tools cannot tell you whether HTTP/2 is actually on in the block that serves traffic. nginx2shell is the standalone, zero-dependency CLI that does the config check those scanners skip. The three other Critical 9.2 flaws from the same release (CVE-2026-121810 HTTP/3, CVE-2026-123634 DNS resolver, CVE-2026-113425 mail proxy) are reported as secondary signals, never as full audits.
Where rivals beat us, honestly: Trivy and Grype cover thousands of CVEs across every dependency you ship; nginx2shell checks exactly the five NGINX2Shell Critical CVEs and says so on every output. Wiz and other cloud tools see the whole fleet inventory at once; nginx2shell v0.1.0 scans one host at a time and has no server mode. Nuclei can prove a remote host is exposed over the network; nginx2shell only reads local files and never proves a remote host is exposed. If you need broad CVE coverage or fleet-wide inventory, use a scanner. If you need to know whether this NGINX on this host is actually exposed to NGINX2Shell, use this tool.
Honest limits
- Only the five NGINX2Shell Critical CVEs are checked. A SAFE verdict means these conditions do not line up, not that the host is safe from every NGINX flaw.
- Distro builds (
nginx/1.24.0 (Ubuntu)) parse from thenginx/X.Y.Zprefix; confirm distro backports in the vendor advisory, the version string alone does not prove the fix. - NGINX Plus builds are reported UNKNOWN: Plus fixed builds differ per CVE (37.0.7.1 / 37.2.0.1 for CVE-2026-123633, 37.0.8.1 / 37.3.0.1 for CVE-2026-123007). Confirm the Plus build in the F5 advisory.
- CVE-2026-123633 also needs low free worker connections, which is runtime state this tool cannot observe; the error log line "worker_connections are not enough" is the signal to check.
- Turning HTTP/2 off does not fix the three secondary Critical flaws (HTTP/3, resolver, mail proxy). The tool reports them as signals.
- The 1.31.8 / 1.30.7 / 1.19.6 / 1.9.4 version fixtures are representative format (version numbers from the advisories); the Plus fixture is labelled SYNTHETIC. The 1.24.0 fixture is recorded from a real binary.
- An EXPOSED verdict is runtime exposure, not proof of exploitability. Your server may never receive the crafted HTTP/2 traffic. The tool never claims otherwise.
The code is on GitHub: techdevfun/nginx2shell. If you run NGINX with HTTP/2 on, run nginx2shell scan and see whether the conditions line up on your hosts before the patch window closes.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.