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

node-cve-2026-106073-check

Offline Node.js evidence checker for CVE-2026-106073: Permission Model realpathSync read bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
124 days agoNot yet reviewed
Share

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

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

node-cve-2026-106073-check

Offline version-evidence checker for CVE-2026-106073 — Node.js: Permission Model realpathSync read bypass.

It compares Node.js versions that you report against the fixed releases named in the Node.js security advisory and labels each one for triage. It is a standard-library Python script that can be copied and run on its own.

  • Offline. It never contacts websites, executes Node.js or project code, or sends exploit payloads. No network mode exists.
  • Evidence, not proof. Results describe reported versions only. Every result carries exploitability: not_tested, and a reported fixed version is not an attestation that a deployed runtime is patched.
  • Conservative. Hidden versions, custom or vendor builds, prereleases, conflicting evidence, and majors outside the rule snapshot remain unknown.
  • You supply the inventory. There is no automatic scan of the current machine, and a public URL is not an inventory.

Contents

  • Requirements
  • Quick start
  • Synthetic report preview
  • Usage
  • Rule snapshot
  • Interpreting results
  • Limits, exit codes and interruption
  • Scope and limitations
  • Sources
  • Project documents
  • Contributing, security and license

Requirements

  • Python 3.10 or newer, standard library only; there are no runtime dependencies. CI runs the tests on Python 3.10 and 3.14 on Ubuntu and Windows.
  • The exact Node.js version of each runtime you want to assess, ideally obtained from the deployed process or container rather than a developer workstation or lockfile.

Quick start

# Assess one version and print JSON to stdout
python node_cve_2026_106073_check.py --version 22.23.4 --format json

# Assess a JSON inventory and save an HTML report (refuses to overwrite an existing file)
python node_cve_2026_106073_check.py --inventory examples/inventory.example.json --format html --output report.html

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

# Show all options, then run the local-only tests
python node_cve_2026_106073_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

At least one of --version, --inventory or --csv-list is required. They can be combined and are assessed in that order.

Options

OptionPurpose
--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). Blank, unknown (default), upstream, official and official_upstream are compared as upstream builds; any other value, such as a vendor name, yields unknown (see Interpreting results).
--permission-model-enabled, --filesystem-read-allowlist, --fs-realpath-syncEach takes true or false. Records an operator observation for the --version inputs. See Precondition observations.
--inventory FILEJSON object or array of entries. Repeatable.
--csv-list FILECSV list with a node_version column. Repeatable.
--format {csv,json,html}Report format. Default: csv. All formats carry the same evidence.
--output FILESave the report to a new file. Default: stdout. The directory must already exist.
--forceReplace an existing output file. Without it, existing reports are protected. Input files can never be 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-versionPrint the tool name and version.

Inventory formats

Both formats accept at most 512 characters per text field. Examples are in examples/inventory.example.json.

JSON is one object or an array of objects. Each record requires integer schema_version: 1 and string node_version. Optional fields are runtime (only "node"), label, build_source, and the observation keys below, each true, false or null. Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected.

CSV requires a header row with a node_version column. Optional columns are label, build_source and the observation columns below, whose cells must be exactly true, false or blank. Undocumented or duplicate columns, rows with a different number of fields than the header, bare quotes inside unquoted cells, and NUL characters are rejected. schema_version and runtime are not CSV columns.

When label is omitted, entries are labelled with the file name (without extension) and entry number.

Precondition observations

Observation keyMeaning
permission_model_enabledpermission model enabled
filesystem_read_allowlistfilesystem read allowlist
fs_realpath_syncfs realpath sync

These are operator-supplied and unverified. They are reported as reported_true, reported_false or not_reported; they never change the version result or establish reachability.

Output

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.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

    385
  • 4

    redforge

    cybersecurity91/redforge

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

    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.

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

    279

Explore all tools

Browse our collection of tools

View all tools →