Offline version-evidence checker for CVE-2026-56848 — Node.js: HTTP/2 reentrant send use-after-free.
It compares Node.js versions that an operator reports against the fixed releases named in the upstream advisory, and writes a CSV, JSON or HTML report. Python 3.10+, standard library only; the executable can be copied alone.
Overview · Quick start · Inputs · Options · Fixed versions · Results · Output · Limits and exit codes · Sources · License
This checker compares operator-reported runtime versions. It never contacts websites, executes Node.js or project code, or sends exploit payloads, and it has no network mode. It does not scan the current machine, and a public URL is not an inventory.
What a result does and does not say:
- A result is version evidence, not a finding of exploitation. Every result carries
exploitability: not_tested. fixed_version_reportedmeans the reported version is at or above the upstream fixed release. It does not attest that the deployed runtime is patched.- Hidden versions, custom builds, conflicting evidence, and uncovered release lines remain
unknown. - Operator-supplied preconditions (HTTP/2 service, untrusted HTTP/2 clients) are recorded but never change the version result or establish reachability.
Collect versions only from systems you are authorized to inspect. Nothing in this repository assesses a deployed target, attests a runtime, or verifies exploitability.
- Python 3.10 or newer. No runtime dependencies; CI runs the tests on Python 3.10 and 3.14 on Ubuntu and Windows.
- The exact Node.js version of each deployed process or container you want to assess, obtained by you outside this tool.
Run from a checkout, or copy node_cve_2026_56848_check.py on its own:
# One runtime, JSON on stdout
python node_cve_2026_56848_check.py --version 22.23.2 --format json
# Synthetic JSON inventory to an HTML report file
python node_cve_2026_56848_check.py --inventory examples/inventory.example.json --format html --output report.html
# CSV inventory; exit 1 if any result is potentially_affected or unsupported_runtime
python node_cve_2026_56848_check.py --csv-list inventory.csv --fail-on-finding
# All options
python node_cve_2026_56848_check.py --helpThe default format is csv, written to stdout unless --output is given. At least one of --version, --inventory or --csv-list is required.
Open the synthetic example report. Example data only; this is not a live assessment.
The three input kinds can be combined in one run. JSON, CSV and HTML reports are built from the same evidence.
Command-line versions. --version (alias --node-version) is repeatable; each value describes a separate runtime. A single leading v and surrounding ASCII whitespace are accepted.
JSON inventory (--inventory FILE, repeatable). One object or an array of objects. See examples/inventory.example.json.
| Field | Required | Type and meaning |
|---|---|---|
schema_version |
yes | Integer 1 |
node_version |
yes | String |
runtime |
no | "node" if present; other runtimes are rejected |
label |
no | String used to identify the entry in reports |
build_source |
no | String; see build source |
http2_service |
no | Boolean or null: http2 service |
untrusted_http2_clients |
no | Boolean or null: untrusted http2 clients |
Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected.
CSV list (--csv-list FILE, repeatable). A header row with a node_version column is required. Optional columns are label, build_source, http2_service and untrusted_http2_clients; observation cells are true, false or blank. schema_version and runtime are not CSV columns. Undocumented or duplicate columns, rows with a different field count, bare quotes inside unquoted cells, NUL characters, and files with no rows are rejected.
build_source (or --build-source) records where the build came from. A blank value, unknown (the default), upstream, official and official_upstream are compared as official upstream builds. Any other value, such as a distribution or vendor name, yields unknown with vendor_build_unverified, because an upstream version number does not show which patches or backports a vendor build contains. Because unknown is compared as upstream, supply the real source for any vendor, distribution or custom build.
| Option | Purpose |
|---|---|
--version VERSION, --node-version VERSION |
Node.js version to assess offline; repeatable |
--build-source SOURCE |
Provenance of every --version build, at most 512 characters; default unknown |
--http2-service {true,false} |
Operator observation applied to every --version input |
--untrusted-http2-clients {true,false} |
Operator observation applied to every --version input |
--inventory FILE |
JSON inventory; repeatable |
--csv-list FILE |
CSV inventory; repeatable |
--format {csv,json,html} |
Report format; default csv |
--output FILE |
Write the report to a new file; default is stdout |
--force |
Explicitly replace an existing output file |
--brand NAME |
Organization name shown in the HTML report, at most 512 characters; ignored by CSV and JSON |
--fail-on-finding |
Exit 1 when any result is potentially_affected or unsupported_runtime |
--tool-version |
Print the tool name and version, then exit |
--help |
Show usage and exit codes |
--output requires an existing directory and a regular-file path. Existing reports are protected unless --force is explicit, and an input file is never overwritten, even with --force.
Reviewed 2026-10-24 against the official release advisory and linked fixed releases (rules_as_of in reports).
| Node.js major | Fixed version |
|---|---|
| 22.x | 22.23.2 |
| 24.x | 24.18.1 |
| 26.x | 26.5.1 |
How these are applied:
- The vendor does not specify an introduced version in the release advisory. Earlier versions of each listed major are therefore
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 by this snapshot and remain
unknown; they are not assumed to be patched. - Old end-of-life majors (0, 4–21, 23 and 25 in the Node.js release schedule reviewed 2026-10-24) are
unsupported_runtime. This is upgrade guidance, not a claim that this particular flaw exists in every historical build. - Prerelease, nightly, release-candidate, package-suffixed, vendor, backported and custom builds need explicit vendor evidence and remain
unknown. Do not label unknown builds safe.
status |
Meaning |
|---|---|
potentially_affected |
The reported version is below the fixed release for its listed major. It needs remediation review; exploitability was not tested. |
fixed_version_reported |
The reported version is at or above the fixed release. This is not a deployed-patch attestation; confirm that the running process or container uses this release. |
unsupported_runtime |
The reported major is end-of-life. Migrate to a supported, fixed release. |
unknown |
Evidence is missing or cannot be classified; see version_status. |
Every result also has a more specific version_status:
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 without a fixed version in the rules |
release_line_not_in_rules |
unknown |
Major not covered by this rule snapshot |
version_not_disclosed |
unknown |
No version was reported |
conflicting_versions |
unknown |
Different versions were reported for one runtime |
qualified_version_unverified |
unknown |
Plain version plus a suffix or prerelease tag |
unrecognized_or_partial_version |
unknown |
Not a full major.minor.patch version |
vendor_build_unverified |
unknown |
Non-upstream build source; checked before the version comparison |
Results also carry evidence_type: operator_reported_version and an evidence_confidence of low, or insufficient when the status is unknown. Reported fixed versions are not verified deployed patches, and version metadata is not a patch or build signature.
Operator preconditions are recorded per result as reported_true, reported_false or not_reported. They are unverified, never change the version result, and are not proof of reachability.
| Inventory observation | Meaning |
|---|---|
http2_service |
http2 service |
untrusted_http2_clients |
untrusted http2 clients |
All formats carry the tool name and version, the report schema version (1.0), the CVE, rules_as_of, the primary sources, and a UTC generated_at. One run timestamp is reused across formats and interruption recovery. It is distinct from rules_as_of and does not attest acquisition time or deployed patches.
JSON is one document with tool, tool_version, report_schema_version, cve, rules_as_of, sources, complete, generated_at and a results array. complete is false for an interrupted run.
CSV quotes every field and neutralizes formula prefixes (=, +, -, @, including after leading whitespace, and leading tab or line-break characters). Notes and sources are joined with |. Columns, in order:
record_type, input_label, input_source, node_version, build_source, status, version_status,
fixed_version, exploitability, evidence_type, evidence_confidence, cve, rules_as_of,
precondition_http2_service, precondition_untrusted_http2_clients, recommendation, notes,
sources, report_schema_version, report_complete, tool, tool_version, generated_at
record_type=result marks a completed assessment. When no result exists, a single record_type=summary row preserves report_complete and the rule metadata without an asset or verdict. Existing column positions are preserved; new columns are appended. NUL characters are rejected before any CSV report is written.
HTML is a single script-free page with a restrictive Content Security Policy, results ordered by severity, the fixed-release table, and an "Interrupted run" notice when complete is false. --brand sets the organization name in the header and footer.
Inputs: regular UTF-8 files only; 4 MiB per file, 100 input files, 10,000 entries in total (counting --version values), and 512 characters per text field. Reports are rendered in memory and published atomically to files. Use stable local copies; file identity checks are not a sandbox against concurrent adversarial mutation.
| Exit | Meaning |
|---|---|
0 |
Run completed. Assessment results do not change this unless --fail-on-finding is set. |
1 |
With --fail-on-finding: at least one potentially_affected or unsupported_runtime result. unknown and fixed_version_reported never exit 1. |
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 behavior:
- Before arguments are validated, nothing is written.
- Otherwise completed results are written with
complete=false(report_complete=falsein CSV) when output is possible. - An interruption after a complete report is published preserves that report and exits 130.
- If publication to a file is 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.
Keep real inventories, targets, reports and secrets outside version control. Synthetic examples are in examples/ and docs/example-report.html.
Reviewed 2026-10-24:
- https://nodejs.org/en/blog/vulnerability/july-2026-security-releases
- https://github.com/nodejs/security-wg/blob/main/vuln/core/186.json
- https://nodejs.org/en/blog/release/v22.23.2
- https://nodejs.org/en/blog/release/v24.18.1
- https://nodejs.org/en/blog/release/v26.5.1
End-of-life majors come from the Node.js release schedule (https://raw.githubusercontent.com/nodejs/Release/main/schedule.json), reviewed 2026-10-24. The schedule lists the 0.x series only partly, 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.
- CLI and evidence reference and implementation status
- Contributing: focused PRs with synthetic fixtures; run
python -m unittest -v,python node_cve_2026_56848_check.py --helpandgit diff --check. Tests never contact real targets. - Security policy for reporting a flaw in this project
- AGPL-3.0 license text and dual licensing: GNU AGPL-3.0 or a separate commercial license from CompleteTech LLC
- Brand assets: CompleteTech LLC names, logos and the artwork in
docs/images/are not covered by the code license
