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

node-cve-2026-106071-check

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

View Repository
Share
Website
123 days agoNot yet reviewed

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

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

node-cve-2026-106071-check

Offline evidence checker for CVE-2026-106071 — Node.js: Permission Model wildcard path over-grant. It compares operator-reported Node.js versions with the fixed release named in the vendor advisory and reports what that evidence does and does not support.

  • Offline and read-only. It 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.
  • Evidence, not verification. Results describe the versions you report. Hidden versions, custom builds, conflicting evidence and uncovered release lines remain unknown. A public URL is not an inventory.
  • Exploitability is never tested. Every result carries exploitability: not_tested.
  • Standard library only. Python 3.10+ with no runtime dependencies; the single executable can be copied on its own.

Contents

  • Requirements and quick start
  • Synthetic report preview
  • Advisory rules
  • Interpreting results
  • Usage
  • Inputs
  • Output and reports
  • Exit codes, interruption and limits
  • Sources
  • Documentation, contributing and license

Requirements and quick start

Requirements: Python 3.10 or newer. Nothing needs to be installed.

Supply an exact version taken from the deployed process (for example from the running container or service), not from a workstation or lockfile:

python node_cve_2026_106071_check.py --version 26.12.1 --format json

Assess a JSON inventory and write an HTML report, or fail a pipeline on findings:

python node_cve_2026_106071_check.py --inventory examples/inventory.example.json --format html --output report.html
python node_cve_2026_106071_check.py --csv-list inventory.csv --fail-on-finding

Show all options and run the local-only test suite:

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

Advisory rules

Reviewed 2026-10-24 against the official release advisory and the linked fixed release. The rule snapshot date is reported as rules_as_of.

Node.js majorFixed version
26.x26.12.1

How a plain, official-upstream version (an optional leading v is accepted) is classified:

Reported versionStatus
Below the fixed version on a listed majorpotentially_affected
The fixed version or a later plain version on the same listed majorfixed_version_reported
A major past end-of-life in the Node.js release scheduleunsupported_runtime
Any other major, or missing, malformed, prerelease, conflicting or vendor/custom/backported evidenceunknown
  • The vendor does not specify an introduced version in the release advisory, so every earlier version of a listed major is treated as potentially_affected.
  • unsupported_runtime is upgrade guidance for end-of-life lines. It is not a claim that this particular flaw exists in every historical build. The end-of-life list comes from the Node.js release schedule, reviewed 2026-10-24.
  • Other active or future majors are not assumed to be patched; they remain unknown.
  • 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.
  • A build_source other than blank, unknown, upstream, official or official_upstream (for example a distribution or vendor name) yields unknown. Vendor, backported and custom builds need vendor evidence.

Interpreting results

StatusMeaning
potentially_affectedThe reported version needs remediation review. It is not confirmed exposure or exploitability.
fixed_version_reportedThe reported version is at or above the upstream fixed release. This is a reported version, not deployed-patch attestation or a safety guarantee.
unsupported_runtimeThe major is end-of-life; migrate to a supported, fixed release.
unknownEvidence is missing or unclassifiable. Missing metadata does not show a runtime is unaffected.

Each result also has a more specific version_status, evidence_type: operator_reported_version, and a low (or, for unknown, insufficient) evidence_confidence. Version metadata is not a patch or build signature.

Precondition observations

You may record three operator-supplied observations alongside a version. They are kept separate: they never change the version result and never establish reachability.

ObservationMeaning
permission_model_enabledpermission model enabled
wildcard_filesystem_grant_directly_under_rootwildcard filesystem grant directly under root
shorter_target_pathshorter target path

Each is true, false or not reported, and appears in reports as reported_true, reported_false or not_reported.

Usage

There is no automatic scan. Provide at least one of --version, --inventory or --csv-list.

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 →