Offline evidence checker for CVE-2026-58044 — Node.js: HTTP header-limit request smuggling. It compares Node.js versions that you report against the fixed releases named in the upstream advisory and writes a CSV, JSON or HTML triage report.
- Scope
- Requirements
- Quick start
- Synthetic report preview
- Usage
- Rule snapshot
- Interpreting results
- Inventory formats
- Report formats
- Limits, exit codes and interruptions
- Data handling
- Sources and provenance
- Project documentation and license
The checker compares operator-reported runtime versions. It is version-evidence triage, not a vulnerability scanner.
- It never contacts websites, executes Node.js or project code, or sends exploit payloads. No network mode is implemented.
- 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 carries
exploitability: not_tested. No exploitation, deployed-patch verification or production assessment is performed or implied. fixed_version_reportedmeans the reported version is at or above the upstream fixed release. It is not proof that the deployed runtime is patched.
- Python 3.10 or later, standard library only. No runtime dependencies; the executable
node_cve_2026_58044_check.pycan be copied alone. - CI runs the local-only unit tests on Python 3.10 and 3.14, on Ubuntu and Windows.
# Assess one version and print a JSON report to stdout
python node_cve_2026_58044_check.py --version 22.23.2 --format json
# Assess a JSON inventory and save an HTML report to a new file
python node_cve_2026_58044_check.py --inventory examples/inventory.example.json --format html --output report.html
# Assess a CSV list; exit 1 if any result is potentially_affected or unsupported_runtime
python node_cve_2026_58044_check.py --csv-list inventory.csv --fail-on-finding
# List all options
python node_cve_2026_58044_check.py --helpAt least one of --version, --inventory or --csv-list is required. The default output format is CSV, written to stdout.
Open the synthetic example report. Example data only; this is not a live assessment.
--version, --inventory and --csv-list can be combined and repeated in one run. Each --version value, and each inventory or CSV entry, describes a separate runtime. JSON, CSV and HTML reports are rendered from the same evidence.
| Option | Purpose |
|---|---|
--version VERSION (alias --node-version) |
Assess an explicitly supplied Node.js version offline. A leading v is accepted. Repeatable. |
--build-source SOURCE |
Provenance of the --version builds, at most 512 characters. The default unknown is compared as upstream, as are upstream, official and official_upstream (ASCII case-insensitive). Any other value, such as a vendor name, yields vendor_build_unverified. |
--forwarding-proxy, --headers-rebuilt-from-incomingmessage, --original-body-piped, --backend-connection-reuse |
Each takes true or false. Records an operator observation for the --version inputs. See Precondition observations. |
--inventory FILE |
JSON object or array of entries. Repeatable. See Inventory formats. |
--csv-list FILE |
CSV list with a node_version column. Repeatable. |
--format csv|json|html |
Report format. Default: csv. |
--output FILE |
Save the report to a new file. Default: 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. |
- Existing reports are protected unless
--forceis explicit. The output directory must already exist. - An input file can never be overwritten, even with
--force. - Reports are rendered fully in memory, then published atomically through a temporary file in the output directory. Without
--forcethe file is published by hard link; on a filesystem without hard links, choose another filesystem or pass--forceexplicitly. - Output goes to stdout when
--outputis omitted.
Reviewed 2026-10-24 against the official release advisory and linked fixed releases (see Sources and provenance).
| Node.js major | Fixed version |
|---|---|
| 22.x | 22.23.2 |
| 24.x | 24.18.1 |
| 26.x | 26.5.1 |
- Introduced version: the vendor does not specify one in the release advisory. For each listed major, versions below its fixed version are
potentially_affectedand require remediation review. - Fixed or later: the listed fixed version and later plain versions on the same major are
fixed_version_reported. - End-of-life majors: Node.js 0.x, 4–21, 23 and 25 produce
unsupported_runtime. The end-of-life dates come from the Node.js release schedule, reviewed 2026-10-24; major 0 is an inference because the schedule lists only 0.8, 0.10 and 0.12. This is upgrade guidance, not a claim that this particular flaw exists in every historical build. - Other majors: any other major, including future ones, is not covered by the snapshot and remains
unknown(release_line_not_in_rules). It is not assumed to be patched. - Prerelease, qualified, vendor, backported and custom builds need explicit vendor evidence and remain
unknown. Do not label unknown builds safe.
Only plain stable versions of the form MAJOR.MINOR.PATCH are compared. Surrounding ASCII whitespace and at most one leading v are ignored.
Each result has a status and a more specific version_status.
status |
Meaning |
|---|---|
potentially_affected |
The reported version is below the fixed release of its major and needs remediation review. This is not confirmed exploitability. |
fixed_version_reported |
The reported version is at or above the fixed release. This is not deployed-patch attestation. Confirm the running process or container actually uses it. |
unsupported_runtime |
The reported major is past end-of-life. Treat as upgrade guidance. |
unknown |
Evidence is missing, conflicting or unclassifiable, or the build is not plain upstream. This is not a statement that the runtime is unaffected. |
version_status |
Condition |
|---|---|
below_fixed_version |
Plain version below the fixed release of a listed major. |
at_or_above_fixed_version |
Plain version at or above the fixed release of a listed major. |
unsupported_release_line |
Plain version on an end-of-life major. |
release_line_not_in_rules |
Plain version on a major that is neither listed nor end-of-life in this snapshot. |
vendor_build_unverified |
A vendor, distribution, custom or unrecognized build source was reported. The upstream version does not show which patches or backports that build contains. |
qualified_version_unverified |
Version carries a suffix, such as a prerelease or package suffix. |
unrecognized_or_partial_version |
Version is not recognizable as MAJOR.MINOR.PATCH. |
version_not_disclosed |
No version was reported. |
conflicting_versions |
Differing version candidates. The engine reports this, but the CLI supplies one version per input. |
Reported fixed versions and verified deployed patches are different things. Version metadata is not a patch or build signature. Every result has evidence_type: operator_reported_version; evidence_confidence is low, or insufficient for unknown.
The advisory describes conditions under which the flaw matters. You can record what you know about them per input. Each value is reported_true, reported_false or not_reported in output.
| Observation key | Meaning |
|---|---|
forwarding_proxy |
forwarding proxy |
headers_rebuilt_from_incomingmessage |
headers rebuilt from incomingmessage |
original_body_piped |
original body piped |
backend_connection_reuse |
backend connection reuse |
Observations are operator-supplied and unverified. They never change the version result or establish reachability.
A file holds one object or an array of 1 to 10,000 records. Each record:
| Field | Required | Notes |
|---|---|---|
schema_version |
yes | Integer 1. |
node_version |
yes | String. |
runtime |
no | Only "node" is accepted. |
label |
no | String. Defaults to <file name without extension>:<position>. |
build_source |
no | String. Defaults to unknown. |
| the four observation keys above | no | Boolean or null. |
Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected. A starting point is in examples/inventory.example.json.
The first row is a header. node_version is required; optional columns are label, build_source and the four observation keys, whose cells are true, false or blank. schema_version and runtime are not CSV columns. Duplicate or undocumented columns, rows with a different number of fields than the header, NUL characters, and bare or unterminated quotes are rejected.
label,node_version,build_source,forwarding_proxy
api-gateway,22.23.2,upstream,true
worker,20.11.0,,All formats share one set of fields per result and one report schema version (1.0).
- JSON: an envelope with
tool,tool_version,report_schema_version,cve,rules_as_of,sources,complete,generated_atandresults. - CSV: every field is quoted and formula prefixes are neutralized, including after leading whitespace. Each completed assessment is a
record_type=resultrow. When no result exists, onerecord_type=summaryrow preservesreport_completeand rule metadata without an asset or verdict.tool,tool_versionandgenerated_atare appended to every result and summary row;report_completeisfalsefor an interrupted run. CSV rejects NUL characters before writing a report. - HTML: a script-free single page with a restrictive content security policy, a results table ordered with
potentially_affectedfirst, thenunsupported_runtime,unknownandfixed_version_reported, the fixed-release table, and a banner when the run was interrupted.
Result fields are input_label, input_source (version, inventory or csv), node_version, build_source, status, version_status, fixed_version, exploitability, evidence_type, evidence_confidence, cve, rules_as_of, one precondition_<key> per observation, recommendation, notes, sources and report_schema_version. In CSV, list values are joined with |.
One UTC report-generation timestamp (generated_at) is captured per CLI run and reused across JSON, CSV, HTML and interruption recovery. It is separate from rules_as_of and is not an evidence-acquisition time.
Regular UTF-8 files only (a BOM is accepted): 4 MiB per file, 100 files, 10,000 entries in total, 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. This is not a verdict; read the report. unknown results and fixed_version_reported results also exit 0. |
| 1 | With --fail-on-finding: at least one 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. See below. |
Completed results are retained whenever output is still possible.
- Before the output path is validated: nothing is written.
- During assessment: completed results are written with
complete: false(report_complete=falsein CSV) and the run exits 130. Assess the remaining inputs again. - After a complete report was published: that report is preserved, nothing is retried, and the run exits 130.
- During file publication: the outcome may be indeterminate. The checker exits 130 without retrying. Inspect the output before retrying; the diagnostic does not establish whether publication succeeded.
- During stdout output: the document can be left partial. A second report is never appended.
Keep real inventories, targets, reports and secrets outside version control. Reports contain the labels and versions you supply. Synthetic examples live in examples/ and docs/example-report.html. Editing or using this repository does not authorize scanning real targets; use assessment features only for systems you are authorized to assess.
- https://nodejs.org/en/blog/vulnerability/july-2026-security-releases
- https://github.com/nodejs/security-wg/blob/main/vuln/core/193.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
The embedded version engine is copied from node-cve-2026-105481-check commit de3161c4a8a7f7ca5c9e531df43b94e2805b52fd; no companion repository is required at runtime. Source-preserving rule metadata is in advisory.json.
- CLI and evidence reference and implementation status
- Contributing: use synthetic fixtures and run
python -m unittest -v,python node_cve_2026_58044_check.py --helpandgit diff --check. Do not contact real targets in tests. - Security policy for reporting flaws in this project
- AGPL-3.0 license and dual licensing: 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
