
Offline Node.js evidence checker for CVE-2026-58040: HTTPS Agent TLS session identity-policy bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.
Offline evidence checker for CVE-2026-58040 — Node.js: HTTPS Agent TLS session identity-policy bypass. It compares operator-reported Node.js runtime versions with the fixed releases named in the vendor advisory and writes a CSV, JSON or script-free HTML triage report. Python 3.10+, standard library only; the executable can be copied alone.
Overview · Quick start · Report preview · Usage · Input files · Interpreting results · Output formats · Limits and exit codes · Limitations · Sources · Documentation · Contributing and license
This repository covers only CVE-2026-58040. The checker evaluates version evidence that you supply; it is triage, not a vulnerability scan.
unknown.exploitability: not_tested. potentially_affected is not confirmed exploitability, and fixed_version_reported is not proof that a deployed runtime is patched. Nothing here claims exploitation or production verification.Requirements: Python 3.10 or later. There is nothing to install; CI runs the tests on Python 3.10 and 3.14 on Ubuntu and Windows.
# One exact runtime version, JSON report on stdout
python node_cve_2026_58040_check.py --version 22.23.2 --format json
# A JSON inventory, saved as an HTML report
python node_cve_2026_58040_check.py --inventory examples/inventory.example.json --format html --output report.html
# Your own CSV list (see Input files), exiting 1 if any result is potentially_affected or unsupported_runtime
python node_cve_2026_58040_check.py --csv-list inventory.csv --fail-on-finding
# Full option list, and the local-only test suite
python node_cve_2026_58040_check.py --help
python -m unittest -v
The default output format is CSV on stdout. Read Interpreting results before acting on a report.
Open the synthetic example report. Example data only; this is not a live assessment.
Provide at least one of --version, --inventory or --csv-list; they can be combined in one run, and all inputs are assessed with the same rules. Option abbreviations are not accepted.
| Option | Purpose |
|---|---|
--version VERSION (alias --node-version) | Assess one explicit Node.js version, offline. A single leading v is accepted. Repeatable; each value describes a separate runtime. |
--build-source SOURCE | Provenance of the --version builds (at most 512 characters). The default unknown, upstream, official and official_upstream are compared as upstream builds; any other value is treated as a vendor, distribution or custom build and the result stays unknown. |
--https-agent-session-reuse {true,false}--different-identity-policies {true,false} | Operator-reported precondition observations, applied to every --version input. Omitted means not reported. See Operator-reported preconditions. |
--inventory FILE | JSON object or array of entries. Repeatable. See Input files. |
--csv-list FILE | CSV list with a node_version column. Repeatable. See Input files. |
--format {csv,json,html} | Report format. Default: csv. All formats carry the same evidence. |
--output FILE | Write the report to a new file instead of stdout. |
--force | Replace an existing --output file. Without it, existing reports are protected. Input files are never 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. Operational errors still exit 2. |
--tool-version, --help | Print the checker name and version, or the full help. |
Precondition flags and --build-source apply only to --version values. For files, set build_source and the observations in each record.
Supply stable local regular UTF-8 files. Keep real inventories, targets, reports and secrets outside version control; synthetic examples are in examples/ and docs/example-report.html.
A JSON inventory is one object or an array of 1 to 10,000 objects. Each record requires integer schema_version: 1 and string node_version. Optional fields are runtime (only "node"), label, build_source, and the two observation keys listed under Operator-reported preconditions, each 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",
"https_agent_session_reuse": null,
"different_identity_policies": null
}
]
A CSV list needs a header row with a node_version column. Optional columns are label, build_source, https_agent_session_reuse and different_identity_policies; observation cells must be exactly true, false or blank. There are no schema_version or runtime columns. Undocumented or duplicate columns, rows with a different field count than the header, quotes inside unquoted cells, text after a closing quote, unterminated quotes, NUL characters and empty lists are rejected.
label,node_version,build_source,https_agent_session_reuse,different_identity_policies
example-service,22.23.2,unknown,,
Each input produces one result. A result is an assessment of reported version evidence against a dated rule snapshot; it never tests exploitability.
Reviewed 2026-10-24 against the official release advisory and linked fixed releases.