Offline version-evidence checker for CVE-2026-58039 — Node.js: Permission Model process-report filesystem bypass.
It compares Node.js versions that an operator reports against the fixed releases named in the Node.js advisory, and writes a CSV, JSON or HTML report. It is a triage aid for version evidence, not a vulnerability scanner or an exploit tool.
- Scope and guarantees
- Requirements
- Quick start
- Synthetic report preview
- Options
- Fixed versions and classification
- Inventory formats
- Output and reports
- Limits, exit codes and interruptions
- Sources
- Project documents
- License and brand
- Offline. The checker 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.
- Operator-reported evidence only. You supply the exact version (and optionally build provenance) taken from the deployed process. A public URL is not an inventory.
- Conservative. Hidden versions, custom builds, conflicting evidence and uncovered release lines remain
unknown. - No exploitation claim. Every result carries
exploitability: not_tested. Apotentially_affectedresult is not confirmed exploitability, andfixed_version_reportedis neither a safety guarantee nor deployed-patch attestation. - Authorization. Use this tool only with inventories for systems you are authorized to assess, and keep real inventories, targets, reports and secrets outside version control.
- Python 3.10 or newer, standard library only. No runtime dependencies; the single executable
node_cve_2026_58039_check.pycan be copied on its own. - CI runs the test suite on Python 3.10 and 3.14 on Ubuntu and Windows.
# Assess one reported version and print JSON
python node_cve_2026_58039_check.py --version 22.23.2 --format json
# Assess an inventory and write an HTML report to a new file
python node_cve_2026_58039_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_58039_check.py --csv-list inventory.csv --fail-on-finding
# Help and tests
python node_cve_2026_58039_check.py --help
python -m unittest -vAt least one of --version, --inventory or --csv-list is required. Without --output, the report goes to stdout; the default format is csv.
Open the synthetic example report. Example data only; this is not a live assessment.
| Option | Meaning |
|---|---|
--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 SOURCE |
Provenance of the --version builds, at most 512 characters. unknown (default), upstream, official and official_upstream (or an empty value) are compared as upstream builds; any other value is treated as a vendor or custom build and stays unknown. |
--permission-model-enabled, --process-report, --filesystem-write-allowlist |
Each takes true or false. Operator observation applied to the --version inputs; it does not change the version result. |
--inventory FILE |
JSON inventory (see Inventory formats). Repeatable. |
--csv-list FILE |
CSV inventory. Repeatable. |
--format {csv,json,html} |
Output format; default csv. All formats carry the same evidence. |
--output FILE |
Write the report to a new file instead of stdout. The directory must already exist. |
--force |
Replace an existing output file. Without it, existing reports are protected. Input files are never overwritten, even with --force. |
--brand NAME |
Organization name shown in the HTML report, at most 512 characters; default CompleteTech LLC. |
--fail-on-finding |
Exit 1 when any result is potentially_affected or unsupported_runtime. |
--tool-version |
Print the checker name and version. Note that --version is the Node.js version to assess, not the checker version. |
Reviewed 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 |
The vendor does not specify an introduced version in the release advisory. 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.
| Status | Meaning |
|---|---|
potentially_affected |
A reported plain version is below the fixed version of its listed major. It needs remediation review. |
fixed_version_reported |
The reported plain version is the listed fixed version or a later one on the same major. This is a reported version, not deployed-patch attestation. |
unsupported_runtime |
The reported major is end-of-life in the Node.js release schedule (majors 0, 4–21, 23 and 25 as reviewed 2026-10-24; major 0 is an inference). This is upgrade guidance, not a claim that this particular flaw exists in every historical build. |
unknown |
Evidence is missing or unclassifiable: no version, conflicting versions, prerelease or otherwise qualified versions, vendor/backported/custom builds (which require vendor evidence), or active/future majors not covered by this rule snapshot. |
Each result also carries a more specific version_status: below_fixed_version, at_or_above_fixed_version, unsupported_release_line, release_line_not_in_rules, vendor_build_unverified, qualified_version_unverified, unrecognized_or_partial_version, conflicting_versions or version_not_disclosed. A reported vendor or custom build source takes precedence: it yields unknown even when the version number would otherwise classify.
Operator-supplied observations never change the version result or establish reachability. They are recorded as reported_true, reported_false or not_reported.
| Observation key | Meaning |
|---|---|
permission_model_enabled |
permission model enabled |
process_report |
process report |
filesystem_write_allowlist |
filesystem write allowlist |
Both formats are regular UTF-8 files. Unknown or undocumented fields are rejected.
JSON (--inventory): one object or a non-empty array of objects. Each record requires integer schema_version: 1 and string node_version. Optional fields are runtime (must be "node"), label, build_source, and the three observation keys above, each boolean or null. Duplicate keys, non-finite numbers and invalid types are rejected. See examples/inventory.example.json.
CSV (--csv-list): a header row with a required node_version column. Optional columns are label, build_source and the three observation columns (true, false or blank). There is no schema_version or runtime column. Duplicate or undocumented columns, rows with a different number of fields than the header, NUL characters, stray quotes and empty lists are rejected.
When no label is given, entries are labeled <file name without extension>:<entry number>; an empty build_source is treated as unknown.
JSON, CSV and HTML use the same evidence and rule snapshot.
- JSON: an object with
tool,tool_version,report_schema_version,cve,rules_as_of,sources,complete,generated_atand aresultsarray. - CSV: one
record_type=resultrow per completed assessment. Every field is quoted, and values starting with a formula prefix (=,+,-,@, after any leading whitespace) are neutralized. When no result exists, a singlerecord_type=summaryrow preservesreport_completeand rule metadata without an asset or verdict. CSV rejects NUL characters before writing a report. - HTML: a single self-contained page without scripts, with explicit evidence type and confidence for each result, and a note when the run was interrupted.
Provenance. Reports retain the checker name and version, rule date, report schema revision and one UTC generation timestamp per run. CSV appends tool, tool_version and generated_at after the existing columns, including on empty and interrupted summary rows. The generation time is not the time the evidence was acquired and is not deployed-patch attestation. Incomplete output remains separate from version conclusions.
Interpreting results. Version metadata is not a patch or build signature. A fixed_version_reported result should be followed by confirming that the running process or container actually uses that release, not only a patched workstation or lockfile. After remediation, redeploy and collect the exact runtime version and build provenance again.
Input limits. Regular files only; 4 MiB per file, 100 input files (--inventory and --csv-list combined), 10,000 entries in total, and 512 characters per text field. Use stable local copies; file identity checks are not a sandbox against concurrent adversarial mutation.
Publication. Reports are rendered in memory first and then published atomically to files, so an encoding or input error leaves no partial file.
| Exit code | Meaning |
|---|---|
0 |
The run completed. |
1 |
A finding with --fail-on-finding. |
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. |
Interruptions.
- Completed rows are retained when output is possible; the report is marked incomplete (
complete: falsein JSON,report_completein CSV). - Before arguments and the output path are validated, nothing is written.
- An interruption after a complete report is published preserves that report and exits 130.
- An interruption during stdout output can leave a partial document and never appends a second report.
- 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.
- https://nodejs.org/en/blog/vulnerability/july-2026-security-releases
- https://github.com/nodejs/security-wg/blob/main/vuln/core/188.json
- https://nodejs.org/en/blog/release/v22.23.2
- https://nodejs.org/en/blog/release/v24.18.1
- https://nodejs.org/en/blog/release/v26.5.1
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: CLI and evidence reference
- Implementation status
- Contributing and security policy
- Synthetic example report and example inventory; keep real inventories out of the repository
Available under the GNU AGPL-3.0 or a separate commercial license from CompleteTech LLC; see LICENSING.md and the license text. Contribution terms are in CONTRIBUTING.md. CompleteTech LLC names, logos and the artwork in docs/images/ are brand assets that are not covered by the code license; see BRAND_ASSETS.md.
