
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.
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.
exploitability: not_tested. A reported fixed version is not an attestation that the deployed process is patched.unknown. A public URL is not an inventory.node_cve_2026_58043_check.py can be copied on its own.--version, --inventory or --csv-list.CI runs the local-only tests and --help on Python 3.10 and 3.14, on Ubuntu and Windows.
# 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.
Open the synthetic example report. Example data only; this is not a live assessment.
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.
| Option | Purpose |
|---|---|
--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 SOURCE | Provenance 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-code | Each takes true or false. Operator-reported observation applied to all --version inputs. |
--inventory FILE | JSON object or array of entries. Repeatable. See Inventory formats. |
--csv-list FILE | CSV with a node_version column. Repeatable. See Inventory formats. |
| Option | Purpose |
|---|---|
--format {csv,json,html} | Report format. Default: csv. |
--output FILE | Save the report to a new file in an existing directory. Default: stdout. |
--force | Replace an existing output file explicitly. |
--brand NAME | Organization name shown in the HTML report (up to 512 characters). Default: CompleteTech LLC. |
--fail-on-finding | Exit 1 when any result is potentially_affected or unsupported_runtime. |
--tool-version | Print 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.
Rules were reviewed on 2026-10-24 against the official release advisory and the linked fixed releases.
| Node.js major | Fixed version |
|---|---|
| 22.x | 22.23.2 |
| 24.x | 24.18.1 |
| 26.x | 26.5.1 |
How versions are classified:
potentially_affected and require remediation.fixed_version_reported.unknown; they are not assumed to be patched.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.unknown. Do not label unknown builds safe.unknown. Missing metadata does not establish that a runtime is unaffected.Version metadata is not a patch or build signature.