Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
node2shell-check — 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. | Kitploit
Tools/GitHubGitHub/completetech-security/node2shell-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisScripting & AutomationConfiguration AuditingInformation GatheringWeb Security
GitHub
Share
completetech-security/node2shell-check

node2shell-check

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.

View RepositoryWebsite
2323 days agoNot yet reviewed

node2shell-check by CompleteTech LLC

Tests Python 3.10+ No dependencies AGPL-3.0 or commercial license

node2shell-check

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_reported is 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.

Contents

  • Requirements
  • Quick start
  • Input modes
  • Understanding results
  • Reports and output
  • Exit codes
  • Scope and limitations
  • Optional tooling
  • Documentation
  • Development and contributing
  • License

Requirements

  • Python 3.10 or later on Windows, macOS, or Linux. There is nothing to install; use python3 where python is not Python 3.
  • Node.js only if you run the optional collector, collect-runtime.cjs.

Quick start

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.

Input modes

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.

ModeOptionNetworkWhat it does
Known version--node-version VERSION (repeatable)NoneCompares a version you obtained elsewhere.
Runtime inventory--inventory FILE (repeatable)NoneReads collector-compatible JSON (schema 1) produced by collect-runtime.cjs.
Website metadataURLs or domains as arguments, or --input FILEYesReads 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.

Understanding results

Each observation receives one of four assessment statuses.

StatusMeaning
potentially_affectedA plain Node.js version below its branch's fix is reported. Verify the deployed build and prioritize remediation.
unsupported_runtimeThe version is on an older, unsupported upstream line. Verify vendor support and move to a supported, patched runtime.
fixed_version_reportedThe reported version meets the fix. This is not independent verification of installed patches.
unknownThe 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 branch22.x24.x26.x
Fixed in22.23.424.22.126.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:

  • Unknown is not an error. A successful request may legitimately reveal no runtime version. Conversely, a 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.
  • Reported is not verified. A version copied from a Dockerfile, deployment label, or public header may differ from the process serving traffic. Headers can be stale, spoofed, or proxy-generated.
  • Vendor builds stay uncertain. Vendor-qualified, custom-built, and pre-release versions remain unknown. Brotli metadata from the collector is context, not a patch verdict.
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    732
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    405
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    342
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    261
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259

Explore all tools

Browse our collection of tools

View all tools →