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
Tools/GitHubGitHub/completetech-security/node-cve-2026-58039-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisScripting & AutomationConfiguration AuditingInformation Gathering
GitHubcompletetech-security/node-cve-2026-58039-check

node-cve-2026-58039-check

Share

Offline Node.js evidence checker for CVE-2026-58039: Permission Model process-report filesystem bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
1323 days agoNot yet reviewed

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

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

node-cve-2026-58039-check

Offline version-evidence checker for CVE-2026-58039 — Node.js: Permission Model process-report filesystem bypass.

It compares Node.js versions that an operator reports against the fixed releases named in the Node.js advisory, and writes a CSV, JSON or HTML report. It is a triage aid for version evidence, not a vulnerability scanner or an exploit tool.

Contents

  • Scope and guarantees
  • Requirements
  • Quick start
  • Synthetic report preview
  • Options
  • Fixed versions and classification
  • Inventory formats
  • Output and reports
  • Limits, exit codes and interruptions
  • Sources
  • Project documents
  • License and brand

Scope and guarantees

  • Offline. The checker never contacts websites, executes Node.js or project code, or sends exploit payloads. There is no network mode and no automatic scan of the current machine.
  • Operator-reported evidence only. You supply the exact version (and optionally build provenance) taken from the deployed process. A public URL is not an inventory.
  • Conservative. Hidden versions, custom builds, conflicting evidence and uncovered release lines remain unknown.
  • No exploitation claim. Every result carries exploitability: not_tested. A potentially_affected result is not confirmed exploitability, and fixed_version_reported is neither a safety guarantee nor deployed-patch attestation.
  • Authorization. Use this tool only with inventories for systems you are authorized to assess, and keep real inventories, targets, reports and secrets outside version control.

Requirements

  • Python 3.10 or newer, standard library only. No runtime dependencies; the single executable node_cve_2026_58039_check.py can be copied on its own.
  • CI runs the test suite on Python 3.10 and 3.14 on Ubuntu and Windows.

Quick start

# Assess one reported version and print JSON
python node_cve_2026_58039_check.py --version 22.23.2 --format json

# Assess an inventory and write an HTML report to a new file
python node_cve_2026_58039_check.py --inventory examples/inventory.example.json --format html --output report.html

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

# Help and tests
python node_cve_2026_58039_check.py --help
python -m unittest -v

At least one of --version, --inventory or --csv-list is required. Without --output, the report goes to stdout; the default format is csv.

Synthetic report preview

Node.js synthetic report

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

Options

OptionMeaning
--version VERSION (alias --node-version)Assess an explicitly supplied Node.js version; a leading v is accepted. Repeatable; each value describes a separate runtime.
--build-source SOURCEProvenance of the --version builds, at most 512 characters. unknown (default), upstream, official and official_upstream (or an empty value) are compared as upstream builds; any other value is treated as a vendor or custom build and stays unknown.
--permission-model-enabled, --process-report, --filesystem-write-allowlistEach takes true or false. Operator observation applied to the --version inputs; it does not change the version result.
--inventory FILEJSON inventory (see Inventory formats). Repeatable.
--csv-list FILECSV inventory. Repeatable.
--format {csv,json,html}Output format; default csv. All formats carry the same evidence.
--output FILEWrite the report to a new file instead of stdout. The directory must already exist.
--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.
--tool-versionPrint the checker name and version. Note that --version is the Node.js version to assess, not the checker version.

Fixed versions and classification

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

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

Result statuses

StatusMeaning
potentially_affectedA reported plain version is below the fixed version of its listed major. It needs remediation review.
fixed_version_reportedThe reported plain version is the listed fixed version or a later one on the same major. This is a reported version, not deployed-patch attestation.
unsupported_runtimeThe reported major is end-of-life in the Node.js release schedule (majors 0, 4–21, 23 and 25 as reviewed 2026-10-24; major 0 is an inference). This is upgrade guidance, not a claim that this particular flaw exists in every historical build.
unknownEvidence is missing or unclassifiable: no version, conflicting versions, prerelease or otherwise qualified versions, vendor/backported/custom builds (which require vendor evidence), or active/future majors not covered by this rule snapshot.

Each result also carries a more specific version_status: below_fixed_version, at_or_above_fixed_version, unsupported_release_line, release_line_not_in_rules, vendor_build_unverified, qualified_version_unverified, unrecognized_or_partial_version, conflicting_versions or version_not_disclosed. A reported vendor or custom build source takes precedence: it yields unknown even when the version number would otherwise classify.

Precondition observations

Operator-supplied observations never change the version result or establish reachability. They are recorded as reported_true, reported_false or not_reported.

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.

    772
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

    420
  • 4

    redforge

    cybersecurity91/redforge

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

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

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

    251

Explore all tools

Browse our collection of tools

View all tools →