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

node-cve-2026-56850-check

Offline Node.js evidence checker for CVE-2026-56850: HTTPS Agent PFX client identity collision. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

View Repository
Share
Website
124 days agoNot yet reviewed

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

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

node-cve-2026-56850-check

Offline evidence checker for CVE-2026-56850 — Node.js: HTTPS Agent PFX client identity collision. It compares Node.js runtime versions that an operator reports against the fixed releases named in the Node.js security advisory, and writes the result as CSV, JSON or script-free HTML.

The checker is a single Python 3.10+ file that uses only the standard library, so the executable can be copied and run on its own.

Contents

  • Scope
  • Requirements
  • Quick start
  • Synthetic report preview
  • Usage
  • Fixed versions
  • Interpreting results
  • Input formats
  • Report formats
  • Limits
  • Exit codes and interruption
  • Data handling
  • Sources and provenance
  • Documentation
  • Contributing, security and license

Scope

This checker triages version evidence. It does not assess a deployed system.

  • It is offline. It never contacts websites, executes Node.js or project code, or sends exploit payloads, and it does not scan the current machine.
  • Its only evidence is the version (and optional build source and precondition observations) that you supply. A public URL is not an inventory.
  • Hidden versions, custom or vendor builds, conflicting evidence, and release lines outside the rule snapshot remain unknown.
  • Every result carries exploitability: not_tested. No result establishes that the flaw is reachable or exploited.
  • A reported fixed version is not verification of a deployed patch. Version metadata is not a patch or build signature.

Use it only with inventories you are authorized to assess.

Requirements

  • Python 3.10 or later; no third-party packages.
  • A Node.js version obtained from the deployed process or container (not from a workstation or lockfile), supplied directly, as a JSON inventory or as a CSV list.

CI runs the unit tests and --help on Python 3.10 and 3.14 on Ubuntu and Windows.

Quick start

# Assess one runtime version and print JSON
python node_cve_2026_56850_check.py --version 22.23.2 --format json

# Assess the synthetic example inventory and save an HTML report
python node_cve_2026_56850_check.py --inventory examples/inventory.example.json --format html --output report.html

# Assess a CSV list and exit 1 if any result is a finding
python node_cve_2026_56850_check.py --csv-list inventory.csv --fail-on-finding

Run python node_cve_2026_56850_check.py --help for the option list, or python -m unittest -v to run the local test suite.

Synthetic report preview

Node.js synthetic report

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

Usage

There is no automatic scan of the current machine. Supply an exact version obtained from the deployed process, then choose an input source and an output format.

Input sources

You can combine any of these in one run; all results go into one report.

OptionInput
--version VERSION (alias --node-version)One Node.js version, such as 22.23.2; a leading v is accepted. Repeatable; each value describes a separate runtime.
--inventory FILEJSON object or array of entries. Repeatable. See JSON inventory.
--csv-list FILECSV with a node_version column. Repeatable. See CSV list.

At least one input is required. JSON, CSV and HTML reports are built from the same evidence.

Options

OptionMeaning
--build-source SOURCEProvenance of the --version builds, at most 512 characters. unknown (the default), upstream, official and official_upstream are compared as upstream builds; any other value, such as a vendor name, yields vendor_build_unverified and a status of unknown.
--shared-https-agent {true,false}Operator observation applied to --version inputs.
--pfx-object-arrays {true,false}Operator observation applied to --version inputs.
--different-client-certificates {true,false}Operator observation applied to --version inputs.
--format {csv,json,html}Report format. The default is csv.
--output FILESave the report to a new file. The default is stdout. The parent directory must already exist.
--forceReplace an existing output file. Without it, an existing output path is an error.
--brand NAMEOrganization name shown in the HTML report, at most 512 characters. The default is CompleteTech LLC.
--fail-on-findingExit 1 when any result is potentially_affected or unsupported_runtime. See Exit codes and interruption.
--tool-versionPrint the checker name and version, then exit. (--version is the Node.js version, not the checker's.)

The three observation options apply only to --version inputs; inventory and CSV entries carry their own observations. For example:

python node_cve_2026_56850_check.py --version 24.18.0 --build-source upstream --shared-https-agent true --format json

Output protection

  • Reports are rendered fully in memory, then written to a temporary file in the output directory and published atomically.
  • An existing output file is never replaced unless --force is explicit.
  • --output must differ from every input file, even with --force. Output must be a regular file path; directories and dangling symbolic links are rejected.
  • Without --force, publication uses a hard link so it cannot overwrite a file; on a filesystem without hard links the run fails with a message to choose another filesystem or use --force.

Fixed versions

Reviewed 2026-10-24 against the official release advisory and linked fixed releases. Advisory-specific caveats are preserved below.

Node.js majorFixed version
22.x22.23.2
24.x24.18.1
26.x26.5.1

The vendor does not specify an introduced version in the release advisory. The rules therefore treat earlier plain versions of each listed major as potentially_affected, and listed fix versions and later plain versions on the same major as fixed_version_reported.

For each listed major, versions below its fixed version require remediation. Unlisted, custom/backported, and prerelease builds need explicit evidence; do not label unknown builds safe.

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 →