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-58043-check — Offline Node.js evidence checker for CVE-2026-58043: Permission Model path-prefix over-grant. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/node-cve-2026-58043-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingUtilities & FrameworksIncident Response
GitHubcompletetech-security/node-cve-2026-58043-check

node-cve-2026-58043-check

Share

Offline Node.js evidence checker for CVE-2026-58043: Permission Model path-prefix over-grant. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
1123 days agoNot yet reviewed

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

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

node-cve-2026-58043-check

Offline evidence checker for CVE-2026-58043: Node.js Permission Model path-prefix over-grant. It compares operator-reported Node.js runtime versions with the fixed releases in the vendor advisory and writes CSV, JSON or HTML triage reports.

  • Offline and read-only. It never contacts websites, executes Node.js or project code, or sends exploit payloads. There is no automatic scan of the current machine.
  • Version evidence, not proof. Every result carries exploitability: not_tested. A reported fixed version is not an attestation that the deployed process is patched.
  • Conservative by design. Hidden versions, custom builds, conflicting evidence and uncovered release lines remain unknown. A public URL is not an inventory.

Contents

  • Requirements
  • Quick start
  • Synthetic report preview
  • Usage
  • Rule snapshot: fixed versions
  • Interpreting results
  • Inventory formats
  • Report formats
  • Limits, exit codes and interruptions
  • Sources
  • Reference, contributing and license

Requirements

  • Python 3.10 or newer, standard library only. No runtime dependencies; the single executable node_cve_2026_58043_check.py can be copied on its own.
  • An exact Node.js version obtained from the deployed process or container, supplied by you with --version, --inventory or --csv-list.

CI runs the local-only tests and --help on Python 3.10 and 3.14, on Ubuntu and Windows.

Quick start

# Assess one reported version and print a JSON report
python node_cve_2026_58043_check.py --version 22.23.2 --format json

# Assess a JSON inventory and save an HTML report
python node_cve_2026_58043_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_58043_check.py --csv-list inventory.csv --fail-on-finding

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

Supply an exact version taken from the deployed process; do not guess it from a lockfile or a workstation. The default output format is csv, written to stdout unless --output is given.

Synthetic report preview

Node.js synthetic report

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

Usage

Inputs

At least one of --version, --inventory or --csv-list is required. They can be combined in one run, and all formats use the same evidence.

OptionPurpose
--version VERSION (alias --node-version)Assess an explicitly supplied Node.js version. Repeatable; each value describes a separate runtime. A single leading v is accepted.
--build-source SOURCEProvenance of the --version builds, up to 512 characters. unknown (default), upstream, official and official_upstream are compared as upstream builds; any other value, such as a vendor name, is treated as a vendor or custom build.
--permission-model-enabled, --filesystem-allowlist, --untrusted-inprocess-codeEach takes true or false. Operator-reported observation applied to all --version inputs.
--inventory FILEJSON object or array of entries. Repeatable. See Inventory formats.
--csv-list FILECSV with a node_version column. Repeatable. See Inventory formats.

Output and exit behavior

OptionPurpose
--format {csv,json,html}Report format. Default: csv.
--output FILESave the report to a new file in an existing directory. Default: stdout.
--forceReplace an existing output file explicitly.
--brand NAMEOrganization name shown in the HTML report (up to 512 characters). Default: CompleteTech LLC.
--fail-on-findingExit 1 when any result is potentially_affected or unsupported_runtime.
--tool-versionPrint the tool name and version.

Existing reports are protected unless --force is explicit, and an input file can never be overwritten, even with --force. Without --force, the report is published without overwriting by hard link; on a filesystem without hard links the checker reports an error, and you must choose another filesystem or pass --force explicitly.

Rule snapshot: fixed versions

Rules were reviewed on 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

How versions are classified:

  • The vendor does not specify an introduced version in the release advisory. For each listed major, versions below its fixed version are potentially_affected and require remediation.
  • The listed fixed version and later plain versions on the same major are fixed_version_reported.
  • Other active or future majors are not covered by this snapshot and remain unknown; they are not assumed to be patched.
  • Majors that the Node.js release schedule lists as end-of-life produce unsupported_runtime. This is upgrade guidance, not a claim that this particular flaw exists in every historical build. The schedule source (see Sources) was reviewed 2026-10-24; the 0.x series is an inference, because the schedule lists only 0.8, 0.10 and 0.12.
  • Unlisted, vendor, distribution, custom or backported builds, and prerelease builds (nightly, rc, package suffixes), need explicit evidence from the vendor and remain unknown. Do not label unknown builds safe.
  • Missing, malformed, partial or conflicting versions remain unknown. Missing metadata does not establish that a runtime is unaffected.

Version metadata is not a patch or build signature.

Interpreting results

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →