Skip to content

About

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.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

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

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

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.

Output and exit behavior

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.

Rule snapshot: fixed versions

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:

  • 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

status Meaning
potentially_affected The reported version is below the fixed release of its major. It needs remediation review; exploitability was not tested.
fixed_version_reported The reported version is at or above the fixed release. This is not deployed-patch attestation: confirm the running process or container actually uses that release.
unsupported_runtime The reported major is past end-of-life. Migrate to a supported, fixed release.
unknown Evidence is missing or cannot be classified. Collect the exact upstream version and build provenance, then run the checker again.

Each result also has a more specific version_status:

version_status Applies when
below_fixed_version Version is below the fixed release of a listed major.
at_or_above_fixed_version Version is at or above the fixed release of a listed major.
unsupported_release_line Major is end-of-life per the release schedule.
release_line_not_in_rules Major is not covered by this rule snapshot.
vendor_build_unverified A vendor, distribution, custom or unrecognized build source was reported; the upstream version does not verify which patches the build contains.
qualified_version_unverified Version has a prerelease or other suffix.
unrecognized_or_partial_version Version cannot be parsed as a plain MAJOR.MINOR.PATCH, or is not text.
conflicting_versions More than one distinct version was reported for one runtime.
version_not_disclosed No version was reported.

Every result has exploitability: not_tested, evidence_type: operator_reported_version, and an evidence_confidence of low or, for unknown results, insufficient.

Precondition observations

You may record whether the advisory's preconditions were observed. These are operator-supplied and unverified. They never change the version result or establish reachability.

Observation Meaning
permission_model_enabled permission model enabled
filesystem_allowlist filesystem allowlist
untrusted_inprocess_code untrusted inprocess code

In reports each observation appears as reported_true, reported_false or not_reported.

Inventory formats

Input files must be regular UTF-8 files. Use stable local copies.

JSON (--inventory): one object or an array. Each record requires integer schema_version: 1 and string node_version. Optional fields are runtime (only "node"), label, build_source, and the three observation keys above, each boolean or null. Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected. A synthetic sample is in examples/inventory.example.json:

[
  {
    "schema_version": 1,
    "label": "example-service",
    "runtime": "node",
    "node_version": "22.23.2",
    "build_source": "unknown",
    "permission_model_enabled": null,
    "filesystem_allowlist": null,
    "untrusted_inprocess_code": null
  }
]

CSV (--csv-list): a header row is required and must include node_version. Optional columns are label, build_source and the observation columns, whose cells are true, false or blank. Undocumented or duplicate columns, rows with a different field count, bare quotes inside unquoted cells, text after a closing quote, unterminated quotes and NUL characters are rejected.

When no label is given, one is generated from the file name and entry number.

Report formats

All formats carry the same assessments and preserve canonical tool, tool_version and UTC generated_at. The timestamp is captured once per CLI run and reused on interrupt recovery; it describes checker generation time, not when an operator observed the runtime. Rule review dates (rules_as_of) remain separate.

  • JSON: an object with tool, tool_version, report_schema_version (1.0), cve, rules_as_of, sources, complete, generated_at and results.
  • CSV: every field is quoted and formula prefixes are neutralized, including after leading whitespace. record_type=result marks completed assessments. When no result exists, a single record_type=summary row preserves report_complete and rule metadata without an asset or verdict. tool, tool_version and generated_at are appended after the existing columns, including on summary rows. List values such as notes and sources are joined with |.
  • HTML: a script-free, self-contained report that sorts results by severity, labels each result's evidence type and confidence, and lists the upstream fixed releases. An interrupted run is flagged as incomplete.

Limits, exit codes and interruptions

  • Input limits: 4 MiB per file, 100 files, 10,000 entries in total (including --version values), and 512 characters per text field.
  • Output: reports are rendered in memory first, so an encoding error occurs before any output, and are atomically published to files. File identity checks are not a sandbox against concurrent adversarial mutation.
Exit code Meaning
0 The run completed. This includes unknown and other assessment results; they are not operational failures.
1 With --fail-on-finding, at least one result is potentially_affected or unsupported_runtime.
2 Usage, input, output or cleanup failure (an operational error, not an assessment result). This does not establish whether report bytes were already written; inspect the output before retrying.
130 Interrupted.

Interruption behavior:

  • Completed rows are written with complete: false (report_complete=false in CSV) when output is still possible.
  • An interruption before the output path is validated writes nothing.
  • An interruption after a complete report is published preserves that report and does not retry.
  • If an interrupt leaves file publication indeterminate, the checker exits 130 without retrying. Inspect the output before retrying; the diagnostic does not establish whether publication succeeded.
  • An interruption during stdout output can leave a partial document and never appends a second report.

Keep real inventories, targets, reports and secrets outside version control.

Sources

Vendor advisory and fixed releases:

End-of-life classification uses the Node.js release schedule, reviewed 2026-10-24.

The embedded version engine is copied from node-cve-2026-105481-check commit de3161c4a8a7f7ca5c9e531df43b94e2805b52fd; no companion repository is required at runtime.

Reference, contributing and license

CompleteTech LLC names, logos and the artwork in docs/images/ are brand assets and are not licensed under the AGPL-3.0 or a commercial code license.

About

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.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages