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
node-cve-2026-58040-check — Offline Node.js evidence checker for CVE-2026-58040: HTTPS Agent TLS session identity-policy bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/node-cve-2026-58040-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration Auditing
GitHubcompletetech-security/node-cve-2026-58040-check

node-cve-2026-58040-check

Offline Node.js evidence checker for CVE-2026-58040: HTTPS Agent TLS session identity-policy bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

View Repository
Share
Website
1124 days agoNot yet reviewed

node-cve-2026-58040-check by CompleteTech LLC

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

node-cve-2026-58040-check

Offline evidence checker for CVE-2026-58040 — Node.js: HTTPS Agent TLS session identity-policy bypass. It compares operator-reported Node.js runtime versions with the fixed releases named in the vendor advisory and writes a CSV, JSON or script-free HTML triage report. Python 3.10+, standard library only; the executable can be copied alone.

Overview · Quick start · Report preview · Usage · Input files · Interpreting results · Output formats · Limits and exit codes · Limitations · Sources · Documentation · Contributing and license

Overview

This repository covers only CVE-2026-58040. The checker evaluates version evidence that you supply; it is triage, not a vulnerability scan.

  • Offline only. It never contacts websites, executes Node.js or project code, or sends exploit payloads. No network mode is implemented.
  • No automatic discovery. It does not scan the current machine. Supply the exact version obtained from the deployed process. A public URL is not an inventory.
  • Conservative results. Hidden versions, custom builds, conflicting evidence, and uncovered branches remain unknown.
  • Not a verification. Every result has exploitability: not_tested. potentially_affected is not confirmed exploitability, and fixed_version_reported is not proof that a deployed runtime is patched. Nothing here claims exploitation or production verification.
  • Authorized use. Use it only for runtimes and inventories you are authorized to assess.

Quick start

Requirements: Python 3.10 or later. There is nothing to install; CI runs the tests on Python 3.10 and 3.14 on Ubuntu and Windows.

# One exact runtime version, JSON report on stdout
python node_cve_2026_58040_check.py --version 22.23.2 --format json

# A JSON inventory, saved as an HTML report
python node_cve_2026_58040_check.py --inventory examples/inventory.example.json --format html --output report.html

# Your own CSV list (see Input files), exiting 1 if any result is potentially_affected or unsupported_runtime
python node_cve_2026_58040_check.py --csv-list inventory.csv --fail-on-finding

# Full option list, and the local-only test suite
python node_cve_2026_58040_check.py --help
python -m unittest -v

The default output format is CSV on stdout. Read Interpreting results before acting on a report.

Synthetic report preview

Node.js synthetic report

Open the synthetic example report. Example data only; this is not a live assessment.

Usage

Provide at least one of --version, --inventory or --csv-list; they can be combined in one run, and all inputs are assessed with the same rules. Option abbreviations are not accepted.

OptionPurpose
--version VERSION (alias --node-version)Assess one explicit Node.js version, offline. A single leading v is accepted. Repeatable; each value describes a separate runtime.
--build-source SOURCEProvenance of the --version builds (at most 512 characters). The default unknown, upstream, official and official_upstream are compared as upstream builds; any other value is treated as a vendor, distribution or custom build and the result stays unknown.
--https-agent-session-reuse {true,false}
--different-identity-policies {true,false}
Operator-reported precondition observations, applied to every --version input. Omitted means not reported. See Operator-reported preconditions.
--inventory FILEJSON object or array of entries. Repeatable. See Input files.
--csv-list FILECSV list with a node_version column. Repeatable. See Input files.
--format {csv,json,html}Report format. Default: csv. All formats carry the same evidence.
--output FILEWrite the report to a new file instead of stdout.
--forceReplace an existing --output file. Without it, existing reports are protected. Input files are never overwritten, even with --force.
--brand NAMEOrganization name shown in the HTML report (at most 512 characters). Default: CompleteTech LLC.
--fail-on-findingExit 1 when any result is potentially_affected or unsupported_runtime. Operational errors still exit 2.
--tool-version, --helpPrint the checker name and version, or the full help.

Precondition flags and --build-source apply only to --version values. For files, set build_source and the observations in each record.

Input files

Supply stable local regular UTF-8 files. Keep real inventories, targets, reports and secrets outside version control; synthetic examples are in examples/ and docs/example-report.html.

JSON inventory

A JSON inventory is one object or an array of 1 to 10,000 objects. Each record requires integer schema_version: 1 and string node_version. Optional fields are runtime (only "node"), label, build_source, and the two observation keys listed under Operator-reported preconditions, each boolean or null. Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected.

[
  {
    "schema_version": 1,
    "label": "example-service",
    "runtime": "node",
    "node_version": "22.23.2",
    "build_source": "unknown",
    "https_agent_session_reuse": null,
    "different_identity_policies": null
  }
]

CSV list

A CSV list needs a header row with a node_version column. Optional columns are label, build_source, https_agent_session_reuse and different_identity_policies; observation cells must be exactly true, false or blank. There are no schema_version or runtime columns. Undocumented or duplicate columns, rows with a different field count than the header, quotes inside unquoted cells, text after a closing quote, unterminated quotes, NUL characters and empty lists are rejected.

label,node_version,build_source,https_agent_session_reuse,different_identity_policies
example-service,22.23.2,unknown,,

Interpreting results

Each input produces one result. A result is an assessment of reported version evidence against a dated rule snapshot; it never tests exploitability.

Fixed versions

Reviewed 2026-10-24 against the official release advisory and linked fixed releases.

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.

    911
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    548
  • 3

    redforge

    cybersecurity91/redforge

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

    366
  • 4

    ARTEX

    baarai/artex

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

    362
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    311
  • 6

    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.

    287

Explore all tools

Browse our collection of tools

View all tools →