Offline version-evidence checker for CVE-2026-106072 — Node.js: TLS noncanonical-IP DNS SAN acceptance.
It compares operator-reported Node.js versions with the fixed releases in the vendor's October 2026 security release and reports JSON, CSV or script-free HTML. It is a single Python file with no dependencies, so the executable can be copied on its own.
- Scope
- Requirements
- Quick start
- Synthetic report preview
- Usage
- Fixed versions and classification
- Interpreting results
- Reports and publication
- Limits, exit codes and interruptions
- Sources
- Project documents
This checker compares operator-reported runtime versions only.
- It never contacts websites, executes Node.js or project code, or sends exploit payloads. No network mode exists.
- It does not scan the current machine. Supply an exact version obtained from the deployed process; a public URL is not an inventory.
- Hidden versions, custom builds, conflicting evidence, and uncovered release lines remain
unknown. - Every result has
exploitability: not_tested. Nothing here confirms exploitation, reachability, or a verified production state. - A reported fixed version is not proof of a deployed patch. Version metadata is not a patch or build signature.
- Python 3.10 or later, standard library only. CI runs Python 3.10 and 3.14 on Ubuntu and Windows.
- Local, regular UTF-8 input files (see limits).
# One reported version, JSON on stdout
python node_cve_2026_106072_check.py --version 22.23.4 --format json
# An inventory file, HTML report saved to a new file
python node_cve_2026_106072_check.py --inventory examples/inventory.example.json --format html --output report.html
# A CSV list; exit 1 if any result is a finding
python node_cve_2026_106072_check.py --csv-list inventory.csv --fail-on-finding
# Help and tests
python node_cve_2026_106072_check.py --help
python -m unittest -vThe 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 inputs contribute to one report that uses the same evidence in JSON, CSV and HTML.
| Option | Purpose |
|---|---|
--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. See build sources. Default unknown. |
--tls-client, --noncanonical-ipv4, --trusted-numeric-dns-san, --resolver-accepts-noncanonical-ip |
Each takes true or false. Operator observation applied to every --version input. |
--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 |
Save the report to a new file in an existing directory. Default: stdout. |
--force |
Replace an existing output file. Inputs still cannot be overwritten. |
--brand NAME |
Organization name in the HTML report, at most 512 characters. Default CompleteTech LLC. |
--fail-on-finding |
Exit 1 if any result is potentially_affected or unsupported_runtime. |
--tool-version |
Print the tool name and version, then exit. |
--build-source and the inventory build_source field describe where the runtime came from. Blank, unknown, upstream, official and official_upstream (compared case-insensitively) are treated as an upstream build and compared by version. Any other value, such as a distribution or vendor name, yields unknown with vendor_build_unverified, because an upstream version does not show which patches or backports that build contains.
JSON is 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 observation keys below, each a boolean or null. Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected. See examples/inventory.example.json.
CSV requires a header row with a node_version column. Optional columns are label, build_source and the observation columns (true, false, or blank). Undocumented or duplicate columns, rows with a different number of fields, bare quotes in unquoted cells, and NUL characters are rejected.
Observation keys (JSON fields, CSV columns, and matching CLI flags with hyphens):
| Observation | Meaning |
|---|---|
tls_client |
Operator reports a TLS client |
noncanonical_ipv4 |
Operator reports noncanonical IPv4 forms |
trusted_numeric_dns_san |
Operator reports a trusted numeric DNS SAN |
resolver_accepts_noncanonical_ip |
Operator reports a resolver that accepts noncanonical IPs |
Observations are operator-supplied and unverified. They are recorded in the report but never change the version result or establish reachability.
Rule snapshot reviewed 2026-10-24 against the official release advisory and the linked fixed releases.
| Node.js major | Fixed version |
|---|---|
| 22.x | 22.23.4 |
| 24.x | 24.22.1 |
| 26.x | 26.12.1 |
- The vendor does not specify an introduced version in the release advisory. For each listed major, versions below its fixed version require remediation and are
potentially_affected. - The listed fixed version and later plain versions on the same major are
fixed_version_reported. - Only plain
MAJOR.MINOR.PATCHversions are compared. Prerelease, nightly/rc, package-suffixed and custom builds need explicit evidence and remainunknown; do not label unknown builds safe. - Other active or future majors are not covered by this snapshot and remain
unknown; they are not assumed to be patched. - Upstream builds of majors past end-of-life in the Node.js release schedule produce
unsupported_runtimeas upgrade guidance. That is not a claim that this particular flaw exists in every historical build. - Vendor, backported and custom builds require vendor evidence and remain
unknown.
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 attestation of the deployed patch or runtime. |
unsupported_runtime |
The reported major is end-of-life. Upgrade guidance, not a finding specific to this flaw. |
unknown |
Evidence is missing or cannot be classified. Missing metadata does not establish that a runtime is unaffected. |
Each result also carries a more specific version_status:
version_status |
Applies to |
|---|---|
below_fixed_version |
potentially_affected |
at_or_above_fixed_version |
fixed_version_reported |
unsupported_release_line |
unsupported_runtime |
version_not_disclosed |
No version reported |
conflicting_versions |
Differing reported versions, or too many candidates for one runtime |
unrecognized_or_partial_version |
Version text that is not a recognizable release |
qualified_version_unverified |
Prerelease, nightly/rc, suffixed or custom version |
vendor_build_unverified |
A vendor, distribution, custom or unrecognized build source |
release_line_not_in_rules |
A major not covered by this rule snapshot |
Other fixed fields: exploitability is always not_tested; evidence_type is operator_reported_version; evidence_confidence is low, or insufficient when the status is unknown. Each result includes a recommendation, notes, and the source links.
All formats are rendered fully in memory before any output, so an encoding error occurs before anything is written.
- JSON is one object with
tool,tool_version,report_schema_version,cve,rules_as_of,sources,complete,generated_atandresults. - CSV quotes every field and neutralizes formula prefixes (
=,+,-,@) after leading whitespace.record_type=resultmarks completed assessments. 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 is a self-contained, script-free document with a restrictive content security policy. It lists results, upstream fixed releases and deployment-verification guidance.
- Provenance: every JSON report, and every CSV result or summary row (including interrupted empty runs), carries
tool,tool_versionandgenerated_at, the UTC report-generation time. A run captures its timestamp once and reuses it across rendering and interruption recovery in every format. This is not evidence-acquisition time or the rule-review date. - File output is staged and published atomically. Existing reports are protected unless
--forceis explicit, and--outputmust differ from every input file even with--force. Without--force, publication uses a hard link, so a filesystem without hard links needs another location or an explicit--force.
Keep real inventories, targets, reports and secrets outside version control. Synthetic examples are in examples/ and docs/example-report.html.
Regular UTF-8 files only; 4 MiB per file, 100 files per run, 10,000 entries per run (including --version values), and 512 characters per text field. Use stable local copies; file identity checks are not a sandbox against concurrent adversarial mutation.
| Code | Meaning |
|---|---|
| 0 | The run completed. |
| 1 | A finding, only with --fail-on-finding: any potentially_affected or unsupported_runtime result. |
| 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 retains completed rows when output is possible and writes them with
complete=false(report_completein CSV, a notice in HTML). Assess the remaining inputs again. - An interruption after a complete report is published preserves that report and exits 130 without a 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.
- https://nodejs.org/en/blog/vulnerability/october-2026-security-releases
- https://nodejs.org/en/blog/release/v22.23.4
- https://nodejs.org/en/blog/release/v24.22.1
- https://nodejs.org/en/blog/release/v26.12.1
End-of-life majors come from the Node.js release schedule, reviewed 2026-10-24 and embedded in the checker; it is not fetched at runtime. The schedule lists 0.x only as 0.8, 0.10 and 0.12, so treating major 0 as end-of-life is an inference.
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
- Security policy
- License and dual licensing: AGPL-3.0 or commercial
- Brand assets: CompleteTech LLC names, logos and the images in
docs/images/are not covered by the code license.
