Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
node-cve-2026-56846-check — Offline Node.js evidence checker for CVE-2026-56846: HTTP/2 retained header memory exhaustion. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/node-cve-2026-56846-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingUtilities & Frameworks
GitHubcompletetech-security/node-cve-2026-56846-check

node-cve-2026-56846-check

Offline Node.js evidence checker for CVE-2026-56846: HTTP/2 retained header memory exhaustion. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

Share
View RepositoryWebsite
1223 days agoNot yet reviewed

node-cve-2026-56846-check by CompleteTech LLC

Tests Python 3.10+ No runtime dependencies AGPL-3.0 or commercial license

node-cve-2026-56846-check

Offline evidence checker for CVE-2026-56846 — Node.js: HTTP/2 retained header memory exhaustion. It compares operator-reported Node.js runtime versions with the fixed releases named in the vendor's security release and writes a conservative, version-only triage report. Python 3.10+, standard library only; the executable can be copied alone.

Version evidence, not an exposure test. Results describe the versions you report. They do not establish that a vulnerable code path is reachable, that a deployed runtime has been patched, or that anything was exploited.

Contents

  • Scope
  • Requirements
  • Quick start
  • Synthetic report preview
  • Usage
  • Fixed versions and classification rules
  • Interpreting results
  • Report formats and provenance
  • Limits, exit codes and interruption
  • Sources
  • Project documents
  • Contributing and security
  • License

Scope

The checker:

  • compares versions you supply (--version, a JSON inventory or a CSV list) with the fixed releases for Node.js 22.x and 24.x;
  • writes CSV (the default), JSON or script-free HTML reports that all carry the same evidence.

The checker never:

  • scans the current machine, contacts websites or any network service, executes Node.js or project code, or sends exploit payloads;
  • tests exploitability: every result carries exploitability: not_tested;
  • attests that a deployed runtime is patched. A reported fixed version is a claim by the operator, not proof of what is running.

Hidden versions, custom builds, conflicting evidence and uncovered release lines remain unknown. A public URL is not an inventory.

Requirements

  • Python 3.10 or later and nothing else: no third-party packages and no network access at runtime. CI runs the tests on Python 3.10 and 3.14 on Ubuntu and Windows.
  • The exact Node.js version obtained from the deployed process or container, and its build source when the build is not an upstream release.
  • Authorization to assess the systems your inventories describe. The tool has no network mode, and running it authorizes nothing.

Quick start

# Assess one reported version and print JSON
python node_cve_2026_56846_check.py --version 22.23.2 --format json

# Assess the synthetic example inventory and save an HTML report
python node_cve_2026_56846_check.py --inventory examples/inventory.example.json --format html --output report.html

# Assess a CSV list (CSV is the default format) and exit 1 on a finding
python node_cve_2026_56846_check.py --csv-list inventory.csv --fail-on-finding

# Show all options, then run the local-only test suite
python node_cve_2026_56846_check.py --help
python -m unittest -v

There is no automatic scan of the current machine: you supply every version. --version is repeatable; each value describes a separate runtime.

Synthetic report preview

Node.js synthetic report

Open the synthetic example report. Example data only; this is not a live assessment.

Usage

Provide at least one input: --version, --inventory or --csv-list. Inputs can be combined in one run, and every input produces its own result row.

Options

OptionPurpose
--version VERSION (alias --node-version)Assess an explicitly supplied Node.js version offline. A leading v is accepted. Repeatable; each value is a separate runtime.
--build-source SOURCEProvenance of the --version builds, at most 512 characters. unknown (the default), upstream, official and official_upstream are compared as upstream releases (matched case-insensitively); any other value, such as a vendor name, yields unknown with vendor_build_unverified.
--http2-service {true,false}Operator observation applied to every --version input.
--untrusted-http2-clients {true,false}Operator observation applied to every --version input.
--inventory FILEJSON object or array of entries. Repeatable.
--csv-list FILECSV list with a node_version column. Repeatable.
--format {csv,json,html}Report format. Default: csv.
--output FILESave the report to a new file in an existing directory. Default: stdout.
--forceReplace an existing output file. Inputs can never be overwritten, even with --force.
--brand NAMEOrganization name shown in the HTML report, at most 512 characters. Default: CompleteTech LLC.
--fail-on-findingExit 1 when a result is potentially_affected or unsupported_runtime (see exit codes).
--tool-versionPrint the tool name and version.

Existing reports are protected unless --force is explicit. --build-source, --brand and the two observation options are checked before any input is read.

JSON inventory

An inventory file holds one object or an array of objects. Each record requires an integer schema_version of 1 and a string node_version. Optional fields are runtime (only "node" is accepted), label, build_source and the two observation keys, each a boolean or null. Unknown keys, duplicate keys, non-finite numbers and invalid types are rejected. See examples/inventory.example.json:

[
  {
    "schema_version": 1,
    "label": "example-service",
    "runtime": "node",
    "node_version": "22.23.2",
    "build_source": "unknown",
    "http2_service": null,
    "untrusted_http2_clients": null
  }
]

CSV list

A CSV list needs a header row with a node_version column. Optional columns are label, build_source, http2_service and untrusted_http2_clients; observation cells hold exactly true, false or nothing. Duplicate or undocumented columns, rows with a different number of fields than the header, bare quotes in unquoted cells and NUL characters are rejected. Entries without a label are named after the file and row.

Operator observations

ObservationMeaning
http2_serviceThe operator reports an HTTP/2 service.
untrusted_http2_clientsThe operator reports untrusted HTTP/2 clients.
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →