Skip to content

About

Offline Node.js evidence checker for CVE-2026-58042: DNS resolveAny process abort. 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-58042-check by CompleteTech LLC

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

node-cve-2026-58042-check

Offline evidence checker for CVE-2026-58042 — Node.js: DNS resolveAny process abort.

It compares Node.js versions that you report against the fixed releases named in the vendor advisory and writes a CSV, JSON or HTML report. Python 3.10+, standard library only; the single executable can be copied on its own.

  • Version evidence only. It never contacts websites, runs Node.js or project code, or sends exploit payloads. There is no network mode and no automatic scan of the current machine.
  • Conservative by design. Hidden versions, custom or vendor builds, conflicting evidence and uncovered release lines stay unknown. A public URL is not an inventory.
  • No exploit verification. Every result carries exploitability: not_tested. A reported fixed version is not proof that the deployed runtime is patched.

Contents

Quick start

Requirements: Python 3.10 or newer. No packages to install.

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

Supply the version of the executable actually used by the serving process. A different node on the host or container PATH may report another version; a package upgrade alone does not establish that an already-running process restarted with it. --version is repeatable; each value describes a separate runtime. The default output format is CSV on stdout.

Report preview

Node.js synthetic report

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

Fixed versions and classification

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

For each listed major, versions below its fixed version require remediation. The vendor does not specify an introduced version in the release advisory, so every earlier version on a listed major is treated as possibly affected.

Reported version Result
Plain version on a listed major, below the fixed version potentially_affected
Fixed version, or a later plain version on the same listed major fixed_version_reported
Plain version on an end-of-life major unsupported_runtime
Any other active or future major unknown (release_line_not_in_rules)
Missing, malformed, conflicting, prerelease, nightly/rc, suffixed or otherwise qualified version unknown
Vendor, distribution, custom or unrecognized build_source unknown (vendor_build_unverified)
  • unsupported_runtime is upgrade guidance, not a claim that this particular flaw exists in every historical build. The end-of-life majors are taken from the Node.js release schedule, reviewed 2026-10-24 (the 0.x series is an inference from that schedule).
  • Vendor, backported and custom builds need vendor evidence, because the upstream version does not show which patches they contain. Unlisted, custom/backported and prerelease builds need explicit evidence; do not label unknown builds safe.
  • Build source is checked before the version: only unknown (the default), upstream, official, official_upstream or blank are compared as upstream builds.
  • A leading v and surrounding ASCII whitespace are ignored; anything else beyond MAJOR.MINOR.PATCH makes the version qualified.

Interpreting results

Status Meaning
potentially_affected The reported version is below the fixed release of its major and needs remediation review. This is not confirmed exploitability.
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, not only a workstation or lockfile.
unsupported_runtime The major is past end of life. Migrate to a supported, fixed release.
unknown Evidence is missing or unclassifiable. Collect the exact upstream version and build provenance of the running process and run the checker again.

Each result also carries a more specific version_status (such as below_fixed_version, at_or_above_fixed_version, unsupported_release_line, release_line_not_in_rules, version_not_disclosed, qualified_version_unverified, unrecognized_or_partial_version or vendor_build_unverified), the applicable fixed_version, a recommendation, and notes. evidence_type is operator_reported_version; evidence_confidence is low, or insufficient for unknown.

Exploitability is never tested. Optional precondition observations are operator-supplied and unverified; they are recorded separately, never change the version result, and do not establish reachability.

Observation key Meaning
dns_resolve_any dns resolve any
untrusted_dns_responses untrusted dns responses

Each observation is reported as reported_true, reported_false or not_reported.

Usage

python node_cve_2026_58042_check.py [options]

At least one of --version, --inventory or --csv-list is required. Run --help for the authoritative option list.

Option Purpose
--version VERSION (alias --node-version) Assess an explicitly supplied version; repeatable.
--build-source SOURCE Provenance of the --version builds (at most 512 characters): unknown (default, compared as upstream), upstream, official, or a vendor name.
--dns-resolve-any {true,false}, --untrusted-dns-responses {true,false} Operator observations applied to --version inputs.
--inventory FILE JSON object or array of entries; repeatable.
--csv-list FILE CSV with a node_version column; repeatable.
--format {csv,json,html} Output format (default csv).
--output FILE Write the report to a new file instead of stdout.
--force Replace an existing output file.
--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 tool name and version.

JSON, CSV and HTML are produced from the same evidence.

Input formats

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 a boolean or null. Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected.

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

CSV list requires a header row with a node_version column. Optional columns are label, build_source and the observation keys (true, false or blank). schema_version and runtime are not CSV columns. Undocumented or duplicate columns, rows with a different number of fields than the header, NUL characters, and malformed quoting are rejected.

A synthetic JSON example is in examples/inventory.example.json.

Output and publication

  • CSV quotes every field and neutralizes formula prefixes (including 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 includes a complete flag and a results array.
  • HTML is a single script-free file with a restrictive content security policy; it displays the report schema and escaped evidence type and confidence.
  • Existing files are protected unless --force is explicit, and an input file can never be overwritten, even with --force. The output directory must already exist.
  • Publication is buffered and atomic: the report is rendered in full, staged, then published. Without --force this uses a hard link, and the checker reports an error on filesystems where hard links are unavailable.

Limits and exit codes

Inputs must be regular UTF-8 files: 4 MiB per file, 100 files per run, 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.

Exit code Meaning
0 The run completed. Findings alone do not change this unless --fail-on-finding is set.
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.

Operational failures (exit 2) are distinct from assessment results.

Interruption. Completed rows are retained and written with complete=false (report_complete=false in CSV) when output is possible; the HTML report shows an interrupted-run notice.

  • An interruption before the output path is validated writes nothing.
  • An interruption after a complete report is published preserves that report and exits 130 without retrying.
  • 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.

Report provenance

JSON, CSV and HTML retain the same UTC generated_at, tool, tool_version, report_schema_version and dated rule identity (rules_as_of) for a run. CSV appends the tool, version and time columns after the existing columns, including in empty or interrupted summaries, without inventing assessments. One timestamp is retained through interruption recovery. It is report generation time, not evidence acquisition time or deployed-patch attestation.

Handling inventories and reports

Keep real inventories, targets, reports and secrets outside version control. Use this tool only for systems you are authorized to assess; editing or running it authorizes nothing further. Synthetic examples are in examples/ and docs/example-report.html.

Sources

The embedded 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.

Further reading, contributing and license

About

Offline Node.js evidence checker for CVE-2026-58042: DNS resolveAny process abort. 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