Offline, version-only triage for CVE-2026-105481: Node.js HTTP keep-alive premature-response acceptance.
node-cve-2026-105481-check compares Node.js versions that you report with the upstream fixed releases for CVE-2026-105481. The flaw is in HTTP Agent connection reuse and can make a client accept a response that was written before its request was sent. The vendor rates it medium severity. The checker is a single Python file with no dependencies.
The checker is offline. It never connects to a target, runs Node.js, inspects a host, or sends a payload. The advisory is version-only, so there is deliberately no network mode.
Important
A version report is evidence, not an assessment. The checker cannot see what actually runs, what a vendor has backported, or whether the vulnerable path is reachable. The vendor does not state an introduced version, so every release below a fix is only "potentially affected". Unlisted, custom, vendor, and prerelease builds are never labelled safe. Every result carries exploitability: not_tested.
- Requirements
- Quick start
- Usage
- Interpreting results
- The report
- Limitations
- Advisory and sources
- Scope
- Documentation
- Contributing and security
- License
Python 3.10 or later on Windows, macOS, or Linux. The checker uses only the standard library, so there is nothing to install. CI runs the tests on Ubuntu and Windows with Python 3.10 and 3.14.
git clone https://github.com/CompleTetech-Security/node-cve-2026-105481-check.git
cd node-cve-2026-105481-check
# Check versions given on the command line (CSV to stdout by default)
python node_cve_2026_105481_check.py --version v22.23.3 --version 24.22.1
# Check the synthetic example inventory and write an HTML report
python node_cve_2026_105481_check.py --inventory examples/inventory.example.json --format html --output report.html
# Check a CSV list, write JSON, and exit 1 if anything needs attention
python node_cve_2026_105481_check.py --csv-list runtimes.csv --format json --output report.json --fail-on-findingRun the tests with python -m unittest -v.
At least one of --version, --inventory, or --csv-list is required. You can combine them, and each entry becomes one result row. A run is limited to 10,000 entries and 100 input files in total.
| Option | Meaning |
|---|---|
--version VERSION (alias --node-version) |
Reported Node.js version. Repeatable. A leading v is accepted. |
--build-source SOURCE |
Provenance of every --version value, at most 512 characters. See build source. |
--http-agent-keepalive, --untrusted-server, --response-queued-before-request true|false |
Operator observations applied to the --version values. They never change status. |
--inventory FILE |
JSON object or array of entries. Repeatable. |
--csv-list FILE |
CSV with a header row. Repeatable. |
--format csv|json|html |
Output format. The default is csv. |
--output FILE |
Write the report to a new file instead of stdout. The file is published atomically. |
--force |
Allow --output to replace an existing file. The output may never replace an input file. |
--brand TEXT |
Organization name shown in the HTML report, at most 512 characters. The default is CompleteTech LLC. |
--fail-on-finding |
Exit 1 when a result is potentially_affected or unsupported_runtime. |
--tool-version, --help |
Print the tool version or usage. |
Input fields, validation rules, and limits are in docs/REFERENCE.md. A synthetic inventory is in examples/inventory.example.json.
--build-source is an operator claim, not verified provenance. The default unknown, and also upstream, official, official_upstream, or an empty value, all allow the normal comparison. An unlabelled version is therefore compared as an upstream build. Any other value is treated as a vendor or custom build, and the result stays unknown.
| Code | Meaning |
|---|---|
| 0 | Completed and the report was written. |
| 1 | Completed with --fail-on-finding and at least one potentially_affected or unsupported_runtime result. |
| 2 | Usage or operational error, such as bad or oversized input, an existing output without --force, or an unwritable output. No partial output file is left. |
| 130 | Interrupted (Ctrl-C). Depending on the stage, completed results are written once and marked incomplete, or nothing is written. A report that was already published is left as written and is not retried. |
Exit 2 means the run itself failed. It is not an assessment result. The stage-by-stage behavior of exit 130 is in docs/REFERENCE.md.
status |
Meaning |
|---|---|
potentially_affected |
The reported upstream version is below the fixed release of its listed major (22.x, 24.x, 26.x). This is not confirmed exploitability. |
fixed_version_reported |
The reported upstream version is at or above that fixed release. This is not a guarantee of safety or of what the deployed binary contains. |
unsupported_runtime |
The major is past end-of-life in the Node.js release schedule. The vendor states that End-of-Life versions are always affected by a security release. |
unknown |
The version is missing, malformed, a prerelease/nightly/rc, a vendor or custom build, conflicting, or in an uncovered major (for example 27.x). |
| Node.js major | 22.x | 24.x | 26.x |
|---|---|---|---|
| Fixed in | 22.23.4 | 24.22.1 | 26.12.1 |
version_statusgives the specific reason for eachstatus.- Precondition observations (
precondition_*) are reported in their own fields and never changestatus. exploitabilityis alwaysnot_tested.evidence_typeis alwaysoperator_reported_version.evidence_confidenceislow, orinsufficientwhenstatusisunknown. It is neverhigh, because the checker cannot inspect the runtime.- A reported fixed version is not a verified deployed patch. Confirm the running process or container, not only a workstation or lockfile.
The full field list and the version-parsing rules are in docs/REFERENCE.md.
--format html writes one self-contained file with no scripts or external requests. --format json and --format csv carry the same fields, and the CSV is formula-injection safe. The screenshots below render the synthetic example inventory; every name in them is made up.
Synthetic example inventory. The full file is docs/example-report.html.
- Completeness. JSON
complete, CSVreport_complete(on every row), and the HTML banner mark an interrupted run. - Provenance. All formats keep the checker name and version, report schema, rule date and sources, completeness, and a UTC ISO 8601
generated_attimestamp. The timestamp is captured once per run and kept when an incomplete report is recovered. It records when the assessment was generated. It is not an evidence-acquisition time or a deployed-patch attestation. - CSV.
tool,tool_version, andgenerated_atfollow the existing columns, including on zero-result summary rows. Cells that could be read as spreadsheet formulas are neutralised. - HTML. Values are escaped. Evidence type and confidence are shown for every result, and the report schema is shown beside the generation time.
- Files.
--outputreports are written with owner-only permissions on POSIX and published atomically. Windows uses the directory's inherited ACL.
Encoding, summary rows, and publication-interruption handling are described in docs/REFERENCE.md.
- The checker reads only what you give it. Absent evidence is never a clean result.
- Vendor, distribution, and custom builds stay
unknown. A version string does not show which patches or backports a build contains. - Majors that the rules do not cover (for example 27.x) stay
unknown. A newer major is not assumed to be patched. - The vendor states no introduced version, so no lower bound is applied below the fixed release.
- The vendor's description implies three preconditions: HTTP Agent keep-alive in use, an untrusted server, and an unsolicited response already queued on an idle socket. They are recorded as operator observations only. They are unverified and never change
status. - It is an incomplete fix of CVE-2026-48931. Earlier fix levels are not modelled separately.
- Nothing here confirms exploitation, reachability, or a production patch level.
| Field | Value |
|---|---|
| CVE | CVE-2026-105481 (vendor severity: medium) |
| Affected | Node.js 22.x, 24.x, and 26.x |
| Fixed in | 22.23.4, 24.22.1, 26.12.1 |
| Sources reviewed | 2026-10-24 |
Primary sources:
- October 2026 security releases
- Release notes: v22.23.4, v24.22.1, v26.12.1
- Node.js release schedule data for lifecycle dates. The same file can be browsed on GitHub.
Release lines past end-of-life are unsupported_runtime, according to the schedule as reviewed on 2026-10-24. Recheck the primary advisories before changing a boundary, and retain contradictory evidence. The per-rule verification table is in docs/REFERENCE.md.
This repository is dedicated to CVE-2026-105481. It has no recorded aliases. Aliases and multiple affected products identify this same exploit; they do not create additional scanner scopes. Fixes for different vulnerabilities belong in independent repositories.
The checker is implemented as an offline version checker with no network mode.
- Reference: inputs, fields, version rules, outputs, exit codes, and source verification
- Implementation checklist: the acceptance contract and its current result
- advisory.json: source-verified advisory record
- AGENTS.md: repository instructions
See CONTRIBUTING.md for development expectations and the contribution terms. Report flaws in this project privately as described in SECURITY.md.
AGPL-3.0, or a separate commercial agreement with CompleteTech LLC. See LICENSING.md. Names, logos, and the images in docs/images/ are CompleteTech LLC brand assets governed by BRAND_ASSETS.md.
Copyright © 2026 CompleteTech LLC. Built by CompleteTech LLC.
