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

node-cve-2026-56847-check

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

View Repository
Share
Website
124 days agoNot yet reviewed

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

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

node-cve-2026-56847-check

Offline version-evidence checker for CVE-2026-56847: Node.js Permission Model trace-log filesystem bypass.

You supply the Node.js versions your runtimes report. The checker compares them with the upstream fixed releases and writes a CSV, JSON or HTML report. It is triage evidence, not an assessment of any deployed system.

  • Purpose and scope
  • Requirements
  • Quick start
  • Synthetic report preview
  • Usage
  • Rule snapshot
  • Interpreting results
  • Reports
  • Limits and failure behavior
  • Limitations
  • Sources and provenance
  • Project reference
  • Contributing, security and license

Purpose and scope

This repository covers only CVE-2026-56847. It compares operator-reported runtime versions with the fixed releases in a dated rule snapshot.

The checker never contacts websites, executes Node.js or project code, or sends exploit payloads. No network mode is implemented. It does not scan the current machine, and a public URL is not an inventory. Running it authorizes nothing: assess only runtimes you are permitted to assess.

Every result carries exploitability: not_tested. Hidden versions, custom builds, conflicting evidence and uncovered release lines remain unknown.

Requirements

  • Python 3.10 or later, standard library only. There are no runtime dependencies, and node_cve_2026_56847_check.py can be copied and used alone.
  • CI runs the unit tests on Ubuntu and Windows with Python 3.10 and 3.14.
  • An exact version string taken from the deployed process, which you must obtain yourself.

Quick start

python node_cve_2026_56847_check.py --version 22.23.2 --format json
python node_cve_2026_56847_check.py --inventory examples/inventory.example.json --format html --output report.html
python node_cve_2026_56847_check.py --csv-list inventory.csv --fail-on-finding
python node_cve_2026_56847_check.py --help
python -m unittest -v

The default format is CSV, written to stdout. --version is repeatable, and each value describes a separate runtime. Existing report files are protected unless --force is explicit.

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 in one run, and all inputs are assessed with the same rules.

Options

OptionPurpose
--version VERSION (alias --node-version)Assess one explicit Node.js version, with or without a leading v. Repeatable; each value is a separate runtime.
--build-source SOURCEProvenance of the --version builds, at most 512 characters. Default unknown, which is compared as upstream. See Interpreting results for how vendor sources are treated.
--permission-model-enabled, --trace-events, --filesystem-write-allowlistOperator observation (true or false) applied to every --version input. See Precondition observations.
--inventory FILEJSON object or array of records. Repeatable.
--csv-list FILECSV with a node_version column. Repeatable.
--format csv|json|htmlReport format. Default csv.
--output FILEWrite the report to a new file. Default is stdout.
--forceReplace an existing output file. Inputs 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.
--tool-version, --helpPrint the tool version, or the full option list and exit-status summary.

The output directory must already exist. Without --force, the checker publishes by hard link and refuses to overwrite; on a filesystem without hard links it stops with an error unless you choose another location or pass --force.

Inventory formats

Both formats feed the same assessment, and JSON, CSV and HTML reports are built from the same evidence. Without a label, a record is named <file name without extension>:<row number>. Use examples/inventory.example.json as a starting point.

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

CSV. Needs a header row with node_version. Optional columns are label, build_source and the observation columns, whose values are exactly true, false or blank. Undocumented or duplicate columns, rows with the wrong number of fields, bare quotes inside unquoted cells, and NUL characters are rejected.

label,node_version,build_source,permission_model_enabled,trace_events,filesystem_write_allowlist
api-example,22.23.1,,true,true,

Precondition observations

ObservationMeaningCLI flag
permission_model_enabledpermission model enabled--permission-model-enabled
trace_eventstrace events--trace-events
filesystem_write_allowlistfilesystem write allowlist--filesystem-write-allowlist

Observations are recorded as reported_true, reported_false or not_reported. They are operator-supplied and unverified. They never change the version result and never establish reachability.

Rule snapshot

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, so earlier versions of each listed major are potentially_affected rather than confirmed affected. The advisory note carried into every result is:

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. The vendor does not specify an introduced version in the release advisory.

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 →