Offline version-evidence checker for CVE-2026-106070, Node.js: ZipFile invalid-header content substitution. It compares Node.js runtime versions that you report against the fixed release named in the vendor advisory and writes a CSV, JSON or HTML triage report. Python 3.10+, standard library only; the executable can be copied alone.
Triage evidence, not an assessment of a deployed system. The checker reads versions you supply. It does not inspect the machine it runs on, run Node.js, or test exploitability, so a result never confirms exploitation or a verified patch.
- Scope and guarantees
- Requirements
- Quick start
- Synthetic report preview
- Inputs
- Command-line options
- Interpreting results
- Fixed versions
- Reports
- Limits and exit codes
- Limitations
- Sources and provenance
- Development
- Security, contributing and license
This repository covers only CVE-2026-106070. The checker is deliberately conservative:
- Offline. It never contacts websites, executes Node.js or project code, or sends exploit payloads. No network mode is implemented.
- Reported versions only. There is no automatic scan of the current machine. Supply an exact version obtained from the deployed process. A public URL is not an inventory.
- Uncertainty stays visible. Hidden versions, custom builds, conflicting evidence, and uncovered branches remain
unknown. Unknown is never reported as safe. - Exploitability is never tested. Every result carries
exploitability: not_tested. - Reported fix is not a verified patch.
fixed_version_reportedsays the reported version is at or above the upstream fixed release. It does not attest that the deployed runtime is patched.
Use it only for inventories you are authorized to assess. Developing or running the checker authorizes no scanning of real targets.
- Python 3.10 or later (CI runs 3.10 and 3.14 on Ubuntu and Windows).
- No third-party packages.
node_cve_2026_106070_check.pyhas no runtime dependencies and can be copied on its own; no companion repository is needed. - Exact Node.js versions taken from the deployed process or container, supplied as
--versionvalues, a JSON inventory or a CSV list.
# One runtime, JSON report on stdout
python node_cve_2026_106070_check.py --version 26.12.1 --format json
# JSON inventory to an HTML report file
python node_cve_2026_106070_check.py --inventory examples/inventory.example.json --format html --output report.html
# CSV list (CSV is the default format), exit 1 on potentially_affected or unsupported_runtime
python node_cve_2026_106070_check.py --csv-list inventory.csv --fail-on-finding
# All options
python node_cve_2026_106070_check.py --help--version is repeatable; each value describes a separate runtime. JSON, CSV and HTML reports are built from the same evidence. Without --output the report goes to stdout.
Open the synthetic example report. Example data only; this is not a live assessment.
A run needs at least one of --version, --inventory or --csv-list; you can combine them and repeat each. Inputs must be regular UTF-8 files within the limits. Synthetic examples are in examples/ and docs/example-report.html.
A version is normalized by stripping ASCII whitespace and at most one leading v. Only a plain stable release (MAJOR.MINOR.PATCH, no leading zeros) is compared. Prereleases, nightly or rc builds, package suffixes, partial versions such as 26.12 and anything longer than 128 characters are unknown.
One object or an array of objects. Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected.
| Field | Required | Notes |
|---|---|---|
schema_version |
yes | Integer 1 |
node_version |
yes | String |
runtime |
no | Only "node" is accepted |
label |
no | Shown in reports; defaults to <file name without extension>:<position> |
build_source |
no | Build provenance, see Build source |
| Observation keys | no | The three keys below; each boolean or null |
[
{
"schema_version": 1,
"label": "example-service",
"runtime": "node",
"node_version": "26.12.1",
"build_source": "unknown",
"zlib_zipfile": null,
"untrusted_zip": null,
"modified_property_or_compaction_before_content_read": null
}
]The header row must include node_version and have no duplicate columns. Optional columns are label, build_source and the observation keys; any other column is rejected, including schema_version and runtime. Observation cells are exactly true, false or blank. Rows must have the same number of fields as the header, and quotes inside unquoted cells, text after a closing quote, unterminated quotes and NUL characters are rejected.
build_source records where the runtime build came from. An empty value, unknown, upstream, official and official_upstream (compared case-insensitively) are treated as an upstream build, so the default unknown is compared as upstream. Any other value is treated as a vendor, distribution or custom build. Its result is unknown because an upstream version number does not show which patches or backports that build contains.
Each record may carry three observations. They are operator-supplied, unverified, and never change the version result or establish reachability.
| Observation key | Advisory precondition |
|---|---|
zlib_zipfile |
zlib zipfile |
untrusted_zip |
untrusted zip |
modified_property_or_compaction_before_content_read |
modified property or compaction before content read |
Reports show each as reported_true, reported_false or not_reported.
| Option | Description |
|---|---|
--version VERSION (alias --node-version) |
Assess an explicitly supplied Node.js version; repeatable. |
--build-source SOURCE |
Build provenance for all --version inputs, at most 512 characters. Default unknown. |
--zlib-zipfile, --untrusted-zip, --modified-property-or-compaction-before-content-read |
true or false; applied to all --version inputs. |
--inventory FILE |
JSON inventory; repeatable. |
--csv-list FILE |
CSV list; repeatable. |
--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. |
--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. |
--build-source and the observation flags apply only to --version inputs; inventory and CSV records carry their own values.
Existing report files are protected unless --force is explicit. The output directory must already exist, and --output must be a regular-file path that differs from every input file, even with --force.
| Status | Meaning |
|---|---|
potentially_affected |
A reported version is below the fixed release of a listed major and needs remediation review. This is not confirmed exposure or exploitation. |
fixed_version_reported |
The reported version is at or above the fixed release. This is not deployed-patch attestation or a safety guarantee. |
unsupported_runtime |
The major is past end-of-life in the Node.js release schedule snapshot. This is upgrade guidance, not a claim that this flaw exists in every historical build. |
unknown |
Evidence is missing, malformed, qualified, from a vendor or custom build, or outside the rules. It must not be treated as safe and needs investigation. |
Each result also has a more specific version_status:
version_status |
Status | Cause |
|---|---|---|
below_fixed_version |
potentially_affected |
Below the fixed release of its major |
at_or_above_fixed_version |
fixed_version_reported |
At or above the fixed release of its major |
unsupported_release_line |
unsupported_runtime |
End-of-life major |
release_line_not_in_rules |
unknown |
Major not covered by this dated rule snapshot |
vendor_build_unverified |
unknown |
Vendor, distribution, custom or unrecognized build source |
qualified_version_unverified |
unknown |
Plain version followed by a suffix, such as a prerelease |
unrecognized_or_partial_version |
unknown |
Not a recognizable MAJOR.MINOR.PATCH version |
version_not_disclosed |
unknown |
No version reported; missing metadata does not show the runtime is unaffected |
Every result has exploitability: not_tested, evidence_type: operator_reported_version, and evidence_confidence of low (insufficient for unknown). Operators should treat unknown results as work to do, not as clean results.
Reviewed 2026-10-24 against the official release advisory and linked fixed releases.
| Node.js major | Fixed version |
|---|---|
| 26.x | 26.12.1 |
- The vendor does not specify an introduced version in the release advisory. Earlier versions of a listed major are
potentially_affectedand require remediation. - A listed fixed version, or a later plain version on the same major, is
fixed_version_reported. - Other active or future majors are not covered and remain
unknown; a newer or unlisted major is not assumed to be patched. - Old end-of-life majors produce
unsupported_runtime. The snapshot treats majors 0 (inferred), 4 through 21, 23 and 25 as end-of-life, based on the Node.js release schedule reviewed 2026-10-24. - Unlisted, custom, backported and prerelease builds need explicit evidence, and vendor or backported builds require vendor evidence. Do not label unknown builds safe.
All formats carry the same evidence. Without --output the report is written to stdout; with --output it is rendered in memory, then published atomically.
JSON has top-level tool, tool_version, report_schema_version (1.0), cve, rules_as_of, sources, complete, generated_at and results. Each result contains:
| Field | Notes |
|---|---|
input_label, input_source |
Label, and where the input came from: version, inventory or csv |
node_version, build_source |
As reported |
status, version_status, fixed_version |
Assessment; fixed_version is empty for unlisted majors |
exploitability, evidence_type, evidence_confidence |
Always not_tested, operator_reported_version, and low or insufficient |
cve, rules_as_of, report_schema_version |
Rule metadata |
precondition_<key> |
One per observation key |
recommendation, notes, sources |
Next step, evidence caveats and source URLs |
CSV has one record_type=result row per completed assessment, using the same fields as columns, followed by report_complete, tool, tool_version and generated_at (also present on the summary row, including for interrupted reports). Lists are joined with |. Every field is quoted, and values that begin with =, +, - or @ (after leading whitespace) or with a tab or line break are prefixed with ' to neutralize formulas. Values containing NUL characters are rejected before any report is written. When no result exists, a record_type=summary row preserves report_complete and rule metadata without an asset or verdict.
HTML is a self-contained, script-free page with a restrictive content-security policy. It sorts results by severity, lists the upstream fixed releases, and shows a callout when the run was interrupted. --brand only changes the organization name in the page.
Reports echo the labels, versions and build sources you supplied, so handle them like the inventory they came from.
Provenance. JSON, CSV and HTML retain the checker name, tool version and one timezone-aware UTC generated_at captured for the run. The timestamp is report generation time, not evidence acquisition time or deployed-patch attestation. Interruption recovery reuses the same timestamp.
| Limit | Value |
|---|---|
| Input file size | 4 MiB per file |
| Input files | 100 per run (--inventory and --csv-list combined) |
| Entries | 10,000 per run (including --version values) |
| Text fields | 512 characters (label, node_version, build_source, --brand) |
Use stable local copies of inputs. File identity checks are not a sandbox against concurrent adversarial mutation.
| Exit code | Meaning |
|---|---|
0 |
The run completed. Findings do not change this unless --fail-on-finding is set. |
1 |
--fail-on-finding is set and a result is potentially_affected or unsupported_runtime. unknown results do not trigger it. |
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. |
- If an interrupt arrives before the output path is validated, nothing is written.
- If it arrives during assessment, completed results are written with the report marked incomplete (
complete: falsein JSON,report_complete=falsein CSV, an interrupted-run notice in HTML). Assess the remaining inputs again. - If it arrives after a complete report was published, that report is preserved and the checker exits 130 without retrying.
- If it leaves file publication indeterminate, the checker exits 130 without retrying. Inspect the output before retrying; the diagnostic does not establish whether publication succeeded.
- If it arrives while writing to stdout, the output may be truncated, and no second report is appended.
- A second interrupt while the partial report is being written may leave no report.
- Results rest on operator-reported version strings. Version metadata is not a patch or build signature.
- Vendor, distribution, backported and custom builds cannot be judged from an upstream version number and remain
unknown. - The vendor gives no introduced version, so
potentially_affectedcovers every earlier release of a listed major, including builds that may not contain the flaw. - Only the rule snapshot dated 2026-10-24 is encoded, and only Node.js 26.x has a fixed version listed.
- Observations about zlib zipfile use, untrusted zip input or modified properties are unverified hints, not proof of reachability.
- Confirm that the running process or container uses the reported release, not only a patched workstation or lockfile, and collect the exact version and build provenance again after remediation.
- Node.js October 2026 security releases
- Node.js v26.12.1 release notes
- Node.js release schedule (end-of-life dates)
The embedded version engine is copied from node-cve-2026-105481-check commit de3161c4a8a7f7ca5c9e531df43b94e2805b52fd; no companion repository is required at runtime. Advisory metadata is recorded in advisory.json.
python -m unittest -v
python node_cve_2026_106070_check.py --helpTests are synthetic and local-only; they never contact real targets. CI runs the same commands on every push and pull request. See docs/IMPLEMENTATION.md for implementation status, docs/REFERENCE.md for the CLI and evidence reference, and CONTRIBUTING.md before opening a pull request.
Keep real inventories, targets, reports and secrets outside version control.
- SECURITY.md: reporting a flaw in this project.
- CONTRIBUTING.md: contribution workflow and the contributor license grant.
- LICENSE and LICENSING.md: GNU AGPL-3.0 or a separate commercial license from CompleteTech LLC.
- BRAND_ASSETS.md: CompleteTech LLC names, logos and repository artwork are not licensed under the AGPL-3.0 or a commercial code license.
