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-58044-check — Offline Node.js evidence checker for CVE-2026-58044: HTTP header-limit request smuggling. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/node-cve-2026-58044-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingIncident Response
GitHubcompletetech-security/node-cve-2026-58044-check

node-cve-2026-58044-check

Offline Node.js evidence checker for CVE-2026-58044: HTTP header-limit request smuggling. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

Share
View RepositoryWebsite
11223 days agoNot yet reviewed

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

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

node-cve-2026-58044-check

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

Scope

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_reported means the reported version is at or above the upstream fixed release. It is not proof that the deployed runtime is patched.

Requirements

  • Python 3.10 or later, standard library only. No runtime dependencies; the executable node_cve_2026_58044_check.py can be copied alone.
  • CI runs the local-only unit tests on Python 3.10 and 3.14, on Ubuntu and Windows.

Quick start

# 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 --help

At least one of --version, --inventory or --csv-list is required. The default output format is CSV, written to stdout.

Synthetic report preview

Node.js synthetic report

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

Usage

--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.

Command-line options

OptionPurpose
--version VERSION (alias --node-version)Assess an explicitly supplied Node.js version offline. A leading v is accepted. Repeatable.
--build-source SOURCEProvenance 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-reuseEach takes true or false. Records an operator observation for the --version inputs. See Precondition observations.
--inventory FILEJSON object or array of entries. Repeatable. See Inventory formats.
--csv-list FILECSV list with a node_version column. Repeatable.
--format csv|json|htmlReport format. Default: csv.
--output FILESave the report to a new file. Default: stdout.
--forceReplace an existing output file.
--brand NAMEOrganization name shown in the HTML report, at most 512 characters. Default: CompleteTech LLC.
--fail-on-findingExit 1 when any result is potentially_affected or unsupported_runtime.
--tool-versionPrint the tool name and version.

Output files

  • Existing reports are protected unless --force is 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 --force the file is published by hard link; on a filesystem without hard links, choose another filesystem or pass --force explicitly.
  • Output goes to stdout when --output is omitted.

Rule snapshot

Reviewed 2026-10-24 against the official release advisory and linked fixed releases (see Sources and provenance).

Node.js majorFixed version
22.x22.23.2
24.x24.18.1
26.x26.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_affected and 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.

Interpreting results

Each result has a status and a more specific version_status.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    772
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    505
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    420
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    260
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    251

Explore all tools

Browse our collection of tools

View all tools →