Skip to content

About

Offline Node.js evidence checker for CVE-2026-106069: TLS leading-zero IPv4 resolver mismatch. 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-106069-check by CompleteTech LLC

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

node-cve-2026-106069-check

Offline version-evidence checker for CVE-2026-106069 — Node.js: TLS leading-zero IPv4 resolver mismatch.

It compares Node.js versions that you report against the fixed releases named in the vendor's advisory and produces CSV, JSON or script-free HTML triage reports. It is a single Python 3.10+ file that uses only the standard library, so the executable can be copied on its own.

Contents

Scope

This checker compares operator-reported runtime versions. It never contacts websites, executes Node.js or project code, or sends exploit payloads, and there is no network mode. It does not scan the current machine: you supply the version evidence.

  • A result is version evidence, not a deployed-system assessment. Every result carries exploitability: not_tested.
  • Hidden versions, custom builds, conflicting evidence, and uncovered branches remain unknown.
  • A public URL is not an inventory. Use an exact version obtained from the deployed process or container.
  • A reported fixed version is not an attestation that the fix is deployed, and no result verifies a production system.
  • Use it only for runtimes you are authorized to review. Nothing in this repository authorizes scanning real targets.

Requirements

  • Python 3.10 or later; no third-party packages.
  • Exact Node.js versions for the runtimes you want to review, from your own records or from the running process.

CI runs the local-only unit tests and the --help check on Ubuntu and Windows with Python 3.10 and 3.14.

Quick start

# Assess one reported version and print JSON to stdout
python node_cve_2026_106069_check.py --version 22.23.4 --format json

# Assess the synthetic inventory and write an HTML report to a new file
python node_cve_2026_106069_check.py --inventory examples/inventory.example.json --format html --output report.html

# Assess a CSV list and exit 1 if any result is a finding
python node_cve_2026_106069_check.py --csv-list inventory.csv --fail-on-finding

# Show all options, or run the local tests
python node_cve_2026_106069_check.py --help
python -m unittest -v

--version is repeatable; each value describes a separate runtime. CSV, JSON and HTML reports contain the same evidence, and the default format is CSV on stdout.

Synthetic report preview

Node.js synthetic report

Open the synthetic example report. Example data only; this is not a live assessment and describes no real system.

Command-line options

Provide at least one of --version, --inventory or --csv-list. Inputs can be combined in one run.

Option Purpose
--version VERSION (alias --node-version) Assess an explicitly supplied Node.js version; a leading v is accepted. Repeatable.
--inventory FILE JSON inventory file (one object or an array). Repeatable.
--csv-list FILE CSV inventory file with a node_version column. Repeatable.
--build-source SOURCE Provenance of the --version builds (see below). Default unknown.
--tls-client {true,false}
--leading-zero-ipv4 {true,false}
--platform-resolver-decimal-behavior {true,false}
Operator-reported observations applied to every --version input.
--format {csv,json,html} Report format. Default csv.
--output FILE Write the report to a new file instead of stdout.
--force Replace an existing output file. Never allows overwriting an input file.
--brand NAME Organization name shown in the HTML report header (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, then exit.

--build-source applies to all --version values in the run. The default unknown, and the values upstream, official, official_upstream or empty (compared case-insensitively), are treated as an upstream build and compared by version. Any other value, such as a vendor name, produces unknown with version_status: vendor_build_unverified, because the upstream version does not show which patches or backports the build contains.

Versions are trimmed of ASCII whitespace and one leading v is accepted. Only plain MAJOR.MINOR.PATCH releases are compared; prerelease, nightly, rc, package-suffixed and partial versions remain unknown.

Existing reports are protected unless --force is explicit, and inputs cannot be overwritten even with --force. The output directory must already exist.

Input formats

Operator-reported observations are optional and are recorded in the report, but they never change the version result or establish reachability.

Observation key CLI flag Advisory precondition
tls_client --tls-client tls client
leading_zero_ipv4 --leading-zero-ipv4 leading zero ipv4
platform_resolver_decimal_behavior --platform-resolver-decimal-behavior platform resolver decimal behavior

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

CSV inventory requires a header row with a node_version column. Optional columns are label, build_source and the observation keys, with values true, false or blank. There are no schema_version or runtime columns. Duplicate or undocumented columns, rows with a different number of fields than the header, quotes inside unquoted cells, text after a closing quote, unterminated quotes, NUL characters, and files with no rows are rejected.

Entries without a label are named after the input file and position (for example inventory:1); --version inputs are labeled Node.js <version>.

Interpreting results

Each result has a status, a more specific version_status, and an exploitability that is always not_tested.

status Meaning
potentially_affected The reported version is below the fixed version of its listed major and needs remediation review. This is not confirmed exploitability.
fixed_version_reported The reported version is at or above the fixed version. This is not attestation of the deployed patch.
unsupported_runtime The reported major is end-of-life. This is upgrade guidance, not a claim that this flaw exists in every historical build.
unknown Evidence is missing or cannot be classified. It is never a statement that the runtime is safe.

The HTML report lists results in the order potentially_affected, unsupported_runtime, unknown, then fixed_version_reported. Evidence confidence is low for classified results and insufficient for unknown.

version_status Status Cause
below_fixed_version potentially_affected Below the fixed version of a listed major.
at_or_above_fixed_version fixed_version_reported At or above the fixed version of a listed major.
unsupported_release_line unsupported_runtime End-of-life major with no fix listed.
release_line_not_in_rules unknown Major not covered by this dated rule snapshot (for example a newer major); it is not assumed to be patched.
vendor_build_unverified unknown A vendor, distribution, custom or unrecognized build source was reported.
qualified_version_unverified unknown A suffix follows the version (prerelease, nightly, package or custom build).
unrecognized_or_partial_version unknown The text is not a plain MAJOR.MINOR.PATCH version.
version_not_disclosed unknown No version was reported.
conflicting_versions unknown The version engine received conflicting candidates. Inventory entries carry one version each, so this is not expected from the command line.

Fixed versions

Rules are as of 2026-10-24, reviewed 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. Earlier versions of each listed major are potentially_affected.
  • A listed fixed version, or a later plain version on the same major, is fixed_version_reported.
  • Other active or future majors remain unknown.
  • End-of-life majors produce unsupported_runtime. They are taken from the Node.js release schedule, reviewed 2026-10-24: majors 4 through 21, 23 and 25, plus major 0 by inference because the schedule lists only 0.8, 0.10 and 0.12.
  • Vendor, backported and custom builds require vendor evidence and remain unknown.
  • 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.

Version metadata is not a patch or build signature.

Reports and output

CSV, JSON and HTML reports are built from the same rows.

  • JSON contains tool, tool_version, report_schema_version, cve, rules_as_of, sources, complete, generated_at and a results array.
  • CSV has one record_type=result row per completed assessment. When no result exists, a single record_type=summary row preserves report_complete and the rule metadata, with no asset or verdict. Every row carries the canonical tool, tool_version and generated_at columns.
  • HTML is a self-contained, script-free page with a restrictive content security policy. --brand changes only the organization name in its header.

Each result row includes the input label and source, the reported version and build source, status, version_status, fixed_version, exploitability, evidence_type (operator_reported_version), evidence_confidence, the CVE, rules_as_of, the three observations (reported_true, reported_false or not_reported), a recommendation, notes, sources and report_schema_version.

Timestamps and versions have separate meanings. generated_at is one UTC run-generation timestamp shared across rows, formats and interruption recovery; it is not evidence-acquisition time. The checker version (tool_version), the report schema (report_schema_version) and the advisory rule date (rules_as_of) are independent.

CSV protections: every field is quoted, and values that start with =, +, - or @ (after leading whitespace), or with a tab, CR or LF, are prefixed with an apostrophe so spreadsheets do not treat them as formulas. NUL characters are rejected before a report is written.

Limits, exit codes and interruption

Input limits. Regular UTF-8 files only (a leading byte-order mark is accepted); 4 MiB per file; 100 input files in total across --inventory and --csv-list; 10,000 entries in total, counting --version inputs; 512 characters per text field.

Publication. Reports are fully rendered in memory and then published atomically to files. Without --force, publication fails rather than replace an existing file; on a filesystem without hard links it fails with an error, so choose another filesystem or use --force explicitly. Use stable local copies of inputs: file identity checks are not a sandbox against concurrent adversarial mutation.

Exit code Meaning
0 The run completed. This does not mean that no findings or unknown results exist.
1 --fail-on-finding was set and a 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. Completed results are retained when output is possible and are written with complete=false (JSON complete, CSV report_complete, and a notice in HTML). Specific cases:

  • Interrupted before the output path was validated: nothing is written.
  • Interrupted after a complete report was published: that report is preserved and the checker exits 130 without retrying.
  • Interrupted while file publication is in progress and the outcome is indeterminate: the checker exits 130 without retrying. Inspect the output before retrying; the diagnostic does not establish whether publication succeeded.
  • Interrupted while writing to stdout: output can be truncated, and a second report is never appended.

Limitations

  • Results are triage evidence from reported versions. They are not runtime attestation, deployed-target assessment or exploit verification, and exploitability is never tested.
  • Version metadata is not a patch or build signature, so vendor, backported and custom builds cannot be classified from the upstream version.
  • Operator-supplied observations are unverified.
  • The rules are a dated snapshot (2026-10-24); majors outside it are not assumed to be patched.
  • The embedded rules do not update themselves; the checker never fetches data.

Keep real inventories, targets, reports and secrets outside version control. Synthetic examples are in examples/ and docs/example-report.html.

Sources

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

Project documents and license

Document Contents
docs/REFERENCE.md CLI and evidence reference
docs/IMPLEMENTATION.md Implementation status and verification
docs/example-report.html Synthetic example report
CONTRIBUTING.md Contribution workflow and licensing of contributions
SECURITY.md Reporting a flaw in this project
BRAND_ASSETS.md Brand and artwork terms
LICENSE and LICENSING.md GNU AGPL-3.0 text and the dual licensing model

To contribute, open a focused issue and pull request with synthetic fixtures, and run python -m unittest -v, python node_cve_2026_106069_check.py --help and git diff --check. Tests must not contact real targets, and rule changes require review of current primary sources. See CONTRIBUTING.md.

This project is available under the GNU AGPL-3.0 or a separate commercial license from CompleteTech LLC; see LICENSING.md. CompleteTech LLC names, logos and the artwork in docs/images/ are not covered by the code license; see BRAND_ASSETS.md.

About

Offline Node.js evidence checker for CVE-2026-106069: TLS leading-zero IPv4 resolver mismatch. 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