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-58045-check — Offline Node.js evidence checker for CVE-2026-58045: zlib synchronous API spoofed TypedArray crash. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/node-cve-2026-58045-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingInformation Gathering
GitHubcompletetech-security/node-cve-2026-58045-check

node-cve-2026-58045-check

Offline Node.js evidence checker for CVE-2026-58045: zlib synchronous API spoofed TypedArray crash. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

Share
View RepositoryWebsite
1224 days agoNot yet reviewed

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

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

node-cve-2026-58045-check

Offline version-evidence checker for CVE-2026-58045 — Node.js: zlib synchronous API spoofed TypedArray crash.

It compares Node.js runtime versions that you report against the fixed releases named in the Node.js security advisory, and writes the result as CSV, JSON or a self-contained HTML report. Python 3.10+, standard library only; the executable is a single file and can be copied on its own.

Contents

  • Scope and honest limits
  • Requirements
  • Quick start
  • Synthetic report preview
  • Usage
  • Inventory formats
  • Fixed versions and classification
  • Interpreting results
  • Report output
  • Limits, exit codes and interruption
  • Handling inventories and reports
  • Sources and provenance
  • Project documents
  • Contributing and security
  • License and brand assets

Scope and honest limits

This repository covers only CVE-2026-58045. The checker is triage evidence, not a runtime assessment.

  • Offline. It never contacts websites, executes Node.js or project code, or sends exploit payloads. No network mode is implemented, so there is no TLS, robots or pacing behavior to configure.
  • No discovery. It does not scan the current machine or any target. A public URL is not an inventory. Supply an exact version obtained from the deployed process, and only for systems you are authorized to inventory.
  • Uncertainty stays visible. Hidden versions, custom builds, conflicting evidence, and uncovered branches remain unknown.
  • Version evidence only. A reported fixed version is not proof of a deployed patch, and a version below the fix is not proof of exploitability. Every result carries exploitability: not_tested.

Requirements

  • Python 3.10 or later; no third-party packages.
  • Exact Node.js version strings from the running process or container (for example, the output of node --version on that runtime, with a leading v accepted).
  • Optionally, the build source (upstream or a vendor name) and operator-reported precondition observations. See Inventory formats.

CI runs the test suite and --help on Python 3.10 and 3.14, on Ubuntu and Windows.

Quick start

# Assess one reported version and print JSON to stdout
python node_cve_2026_58045_check.py --version 22.23.2 --format json

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

# Assess your own CSV list (CSV to stdout by default); exit 1 on a finding
python node_cve_2026_58045_check.py --csv-list inventory.csv --fail-on-finding

# Show all options, then run the local tests
python node_cve_2026_58045_check.py --help
python -m unittest -v

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; otherwise the checker reports a usage error. The three sources can be combined in one run, and every input becomes one result row. JSON, CSV and HTML are rendered from the same evidence.

OptionDescription
--version VERSION (alias --node-version)Assess an explicitly supplied Node.js version. Repeatable; each value describes a separate runtime. A leading v is accepted.
--build-source SOURCEProvenance of the --version builds, at most 512 characters. unknown (the default), upstream, official or official_upstream are compared as upstream; any other value, such as a vendor name, yields unknown with vendor_build_unverified.
--zlib-synchronous-api {true,false}Operator-reported observation applied to the --version inputs.
--attacker-controlled-typedarray-object {true,false}Operator-reported observation applied to the --version inputs.
--inventory FILEJSON object or array of entries. Repeatable.
--csv-list FILECSV with a node_version column. Repeatable.
--format {csv,json,html}Report format. Default: csv.
--output FILESave the report to a new file. Default: stdout.
--forceReplace an existing output file. Without it, an existing file is never overwritten.
--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. See exit codes.
--tool-versionPrint the tool name and version.

Output protections:

  • --output must name a file in an existing directory. An existing report is protected unless --force is explicit, and an input file cannot be overwritten even with --force.
  • Reports are rendered fully in memory, then published atomically to files. Without --force the checker publishes with a hard link and fails with an error rather than overwrite if the filesystem cannot do that.
  • The precondition flags and --build-source apply only to --version inputs; inventory and CSV entries carry their own values.

Inventory formats

Inventories are optional; --version needs none. Inventory entries may include operator-reported precondition observations. These never change the version result or establish reachability.

Observation keyMeaning
zlib_synchronous_apiOperator-reported: zlib synchronous API
attacker_controlled_typedarray_objectOperator-reported: attacker-controlled TypedArray object

Each observation is true, false or unreported, and appears in results as reported_true, reported_false or not_reported.

JSON (--inventory)

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.

    916
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    558
  • 3

    redforge

    cybersecurity91/redforge

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

    370
  • 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.

    360
  • 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.

    317
  • 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.

    289

Explore all tools

Browse our collection of tools

View all tools →