Passive Node2Shell (CVE-2026-111497) exposure checker and offline Node.js runtime assessment with branded HTML reports. Python 3.10+, no dependencies, no exploit payloads.
Version-based triage for Node2Shell (CVE-2026-111497) in Node.js runtimes and websites
Offline runtime assessment · passive website metadata · single-file, dependency-free Python
node2shell-check compares the Node.js version a runtime or website reports with the official upstream fix for each supported branch. You can assess a version you already know, collect metadata inside a deployed service, or inspect a website's ordinary public response.
It sends no exploit payloads, never decodes Brotli, and reports uncertainty honestly: a hidden, vendor-built, or conflicting version is unknown, never "safe".
[!IMPORTANT] Potential exposure is not confirmed exploitability. Every result keeps exploitability
not_tested. The vulnerability involves decoding attacker-controlled Brotli data, and a version alone cannot show whether an application reaches that code path.fixed_version_reportedis not verification of a deployed patch. Treat every result as a prompt for an administrator to check.
Check only targets you are authorized to assess, and keep real target lists, inventories, and reports out of version control.
python3 where python is not Python 3.collect-runtime.cjs.git clone https://github.com/completetech-security/node2shell-check.git
cd node2shell-check
# Compare a known version. Offline, no network calls.
python node2shell_check.py --node-version 24.22.0
# Collect metadata where the service runs (same Node.js binary), then assess it offline.
node collect-runtime.cjs > runtime.json
python node2shell_check.py --inventory runtime.json --format html --output report.html
# Check authorized websites listed one per line (start from websites.example.txt).
cp websites.example.txt websites.txt # then replace the entries with your own authorized targets
python node2shell_check.py --input websites.txt --format html --output websites-report.html
With no --format, results are written as CSV to stdout. Run python node2shell_check.py --help for the complete option list, or see the full reference.
All three modes can be combined in one run. Each input becomes its own observation with its own evidence; a supplied runtime version is never assumed to belong to a supplied URL.
| Mode | Option | Network | What it does |
|---|---|---|---|
| Known version | --node-version VERSION (repeatable) | None | Compares a version you obtained elsewhere. |
| Runtime inventory | --inventory FILE (repeatable) | None | Reads collector-compatible JSON (schema 1) produced by collect-runtime.cjs. |
| Website metadata | URLs or domains as arguments, or --input FILE | Yes | Reads public response metadata from each supplied target. |
Runtime inventory. collect-runtime.cjs records version and build metadata from the Node.js binary that runs it. It never loads application code, reads environment variables, decompresses data, or opens a connection. It cannot attest vendor patch provenance, and its build_source defaults to unknown. Run it in the actual container or runtime you intend to assess; a host installation does not describe every container, function, or worker.
Website metadata. For each target the checker reads robots.txt and, if policy allows, makes an ordinary GET request to the supplied page. It uses verified TLS, an honest User-Agent, bounded responses, and request pacing. Redirects stay on the same host or its www counterpart, and HTTPS downgrades stop. It fetches nothing else and sends no compressed bodies, credentials, or crafted requests. Express or Next.js hints never become Node.js version evidence, and Brotli response compression does not prove that an application decodes request bodies. See Requests made in website mode for the full rules.
Each observation receives one of four assessment statuses.
| Status | Meaning |
|---|---|
potentially_affected | A plain Node.js version below its branch's fix is reported. Verify the deployed build and prioritize remediation. |
unsupported_runtime | The version is on an older, unsupported upstream line. Verify vendor support and move to a supported, patched runtime. |
fixed_version_reported | The reported version meets the fix. This is not independent verification of installed patches. |
unknown | The version is missing, malformed, conflicting, vendor-qualified, custom-built, pre-release, possibly backported, or outside this rule snapshot. |
Upstream fixes in the embedded rule snapshot:
| Node.js branch | 22.x | 24.x | 26.x |
|---|---|---|---|
| Fixed in | 22.23.4 | 24.22.1 | 26.12.1 |
Thresholds come from the Node.js October 2026 security releases and the release notes for 22.23.4, 24.22.1, and 26.12.1, released 2026-10-21. The embedded rule snapshot is dated 2026-10-23. The checker does not download or refresh rules, so rerunning an old copy does not update them.
Keep these distinctions in mind when reading a report:
fixed_version_reported observation elsewhere in a report does not erase an unsuccessful website check. Inspect each result's fetch outcome and the run's completeness as well as its assessment.unknown. Brotli metadata from the collector is context, not a patch verdict.