Skip to content

About

Offline Node.js evidence checker for CVE-2026-58041: SQLite cached iterator write replay. 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-58041-check by CompleteTech LLC

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

node-cve-2026-58041-check

Offline version-evidence checker for CVE-2026-58041 — Node.js: SQLite cached iterator write replay.

The checker compares operator-reported Node.js runtime versions with the fixed releases in a dated rule snapshot (reviewed 2026-10-24). It never contacts websites, executes Node.js or project code, or sends exploit payloads, and there is no network mode. Hidden versions, custom builds, conflicting evidence, and uncovered branches remain unknown. A public URL is not an inventory.

Results are triage evidence, not a runtime assessment: every result has exploitability: not_tested, and no deployed-target assessment, runtime attestation or exploit verification is claimed.

Synthetic report preview

Node.js synthetic report

Open the synthetic example report. Example data only; this is not a live assessment.

Requirements

  • Python 3.10 or newer, standard library only. There are no runtime dependencies, and the executable node_cve_2026_58041_check.py can be copied alone.
  • An exact Node.js version obtained from the deployed process or container. The checker does not scan the current machine.

Quick start

python node_cve_2026_58041_check.py --version 24.18.1 --format json

Without --format, the report is CSV. Output goes to stdout unless --output is given.

Usage

# Several runtimes at once (each --version is a separate runtime)
python node_cve_2026_58041_check.py --version 24.18.1 --version 26.5.0 --format json
# JSON inventory to an HTML report file
python node_cve_2026_58041_check.py --inventory examples/inventory.example.json --format html --output report.html
# CSV inventory; exit 1 if any result is a finding
python node_cve_2026_58041_check.py --csv-list inventory.csv --fail-on-finding
# Help and local synthetic tests
python node_cve_2026_58041_check.py --help
python -m unittest -v

At least one of --version, --inventory or --csv-list is required. All three can be combined and each can be repeated; every --version value describes a separate runtime. JSON, CSV and HTML reports are built from the same evidence.

Options

Option Purpose
--version VERSION (alias --node-version) Assess an explicitly supplied Node.js version offline; a leading v is accepted. Repeatable.
--build-source SOURCE Provenance of the --version builds, at most 512 characters. Default unknown, which is compared as upstream. upstream, official and official_upstream are also treated as upstream; any other value (such as a vendor name) yields vendor_build_unverified.
--sql-tag-store, --stale-iterator, --cached-statement-rebinding Operator observation (true or false) applied to the --version inputs. See Interpreting results.
--inventory FILE JSON object or array of entries. Repeatable.
--csv-list FILE CSV with a node_version column. Repeatable.
--format csv|json|html Report format. Default csv.
--output FILE Write the report to a new file instead of stdout. The directory must already exist.
--force Replace an existing output file. Inputs can never be 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, --help Print the tool version or the help text.

Existing report files are protected unless --force is explicit.

Reported fixed versions

Reviewed 2026-10-24 against the official release advisory and linked fixed releases. These are versions the vendor reports as fixed; the checker cannot verify that a given deployment actually runs them.

Node.js major Fixed version
24.x 24.18.1
26.x 26.5.1

How versions are classified:

  • The vendor does not establish an introduced version. Versions below the fixed version of a listed major are potentially_affected and require remediation.
  • Listed fix versions and later plain versions on that same major are fixed_version_reported.
  • Other active or future majors remain unknown; a newer or unlisted major is not assumed to be patched.
  • Old end-of-life majors produce unsupported_runtime as upgrade guidance, not as a claim that this particular flaw exists in every historical build. End-of-life is taken from the Node.js release schedule (https://raw.githubusercontent.com/nodejs/Release/main/schedule.json, reviewed 2026-10-24).
  • Prerelease, custom, backported and vendor builds need explicit vendor evidence and remain unknown. Do not label unknown builds safe.

Source conflict: Node.js 22.x

The sources disagree about Node.js 22.x, and the conflict is unresolved:

  • The nodejs.org July 2026 security releases page says the issue affects all users in active release lines 26.x and 24.x. 22.x is not named, although v22.23.2 is in the same release batch.
  • security-wg vuln/core/190.json lists vulnerable 24.x || 26.x and patched ^24.18.1 || ^26.5.1, but its overview text says it affects 22.x, 24.x and 26.x.
  • The CVE record (CVE-2026-58041 on cveawg.mitre.org) has the same 22.x, 24.x and 26.x text, with affected <=22.23.1, <=24.18.0 and <=26.5.0.

No 22.x fixed version is asserted for this CVE, so 22.x is deliberately not listed as affected or fixed and must stay unknown unless explicit evidence is obtained.

Interpreting results

Status Meaning
potentially_affected The reported version is below the fixed release of its major and 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 or a safety guarantee; confirm that the running process actually uses it.
unsupported_runtime The major is end-of-life. This is upgrade guidance only.
unknown Evidence is missing or unclassifiable: no version, malformed, conflicting or prerelease versions, vendor or custom builds, and majors not covered by the rules.

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.

Every result has exploitability: not_tested. Operator-supplied observations are unverified, never change the version result, and do not establish reachability:

Observation Meaning
sql_tag_store sql tag store
stale_iterator stale iterator
cached_statement_rebinding cached statement rebinding

Inventory formats

Synthetic examples are in examples/; start from examples/inventory.example.json.

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

CSV requires a header row with node_version. Optional columns are label, build_source and the observation columns, whose values are true, false, or blank:

label,node_version,build_source,sql_tag_store,stale_iterator,cached_statement_rebinding
api-a,24.18.0,upstream,,,
api-b,26.5.1,,true,false,

Output and provenance

All formats carry the same evidence for each input: status, version_status, fixed version, exploitability, evidence type and confidence, CVE, rules date, observations, recommendation, notes and sources.

  • CSV quotes every field and neutralizes formula prefixes after leading whitespace. Completed assessments use record_type=result; when no result exists, a record_type=summary row preserves report_complete and rule metadata without an asset or verdict. NUL characters are rejected before a report is written.
  • JSON is one document with top-level tool, tool_version, report_schema_version, cve, rules_as_of, sources, complete, generated_at and results.
  • HTML is a self-contained, script-free report. The input values are escaped, and the page sets a restrictive content security policy.
  • Provenance: CSV appends canonical tool, tool_version and UTC generated_at columns to every result and empty summary; JSON and HTML use the same report context. Generation time is captured once per run and reused if an interrupted report is recovered. It is assessment time, not advisory or runtime evidence time. Existing CSV column positions, formula protection and publication guarantees remain unchanged.
  • Interrupted runs are marked incomplete (report_complete=false in CSV, complete: false in JSON, a notice in HTML).

Limits and exit codes

  • Regular UTF-8 files only; 4 MiB per file, 100 files, 10,000 entries total, 512 characters per text field.
  • Reports are buffered and atomically published to files. Use stable local copies; file identity checks are not a sandbox against concurrent adversarial mutation.
Exit code Meaning
0 The run completed.
1 A finding (potentially_affected or unsupported_runtime) 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.

Interruption handling:

  • Interruptions retain completed rows (marked incomplete) when output is possible. An interruption before the output path is validated writes nothing.
  • Interruption during stdout output can leave a partial document and never appends a second report.
  • An interruption after a complete report is published preserves that report and exits 130.
  • 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.

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

Documentation

Sources

The embedded version engine is copied from node-cve-2026-105481-check commit de3161c4a8a7f7ca5c9e531df43b94e2805b52fd; no companion repository is required at runtime. Version metadata is not a patch or build signature.

Contributing and security

Read CONTRIBUTING.md and AGENTS.md before changing the project. This repository covers only CVE-2026-58041: use synthetic fixtures, never contact real targets in tests, and keep unknown evidence uncertain. Report flaws in this project as described in SECURITY.md. Use the checker only for systems you are authorized to assess.

License and brand assets

Available under the GNU AGPL-3.0 (LICENSE) or a separate commercial license from CompleteTech LLC; see LICENSING.md. CompleteTech LLC names, logos and the repository artwork are not covered by the code license; see BRAND_ASSETS.md. The external advisory sources above are not relicensed by this repository.

Copyright © 2026 CompleteTech LLC.

About

Offline Node.js evidence checker for CVE-2026-58041: SQLite cached iterator write replay. 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