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-58041-check — Offline Node.js evidence checker for CVE-2026-58041: SQLite cached iterator write replay. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/node-cve-2026-58041-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisScripting & AutomationConfiguration AuditingInformation Gathering
GitHubcompletetech-security/node-cve-2026-58041-check

node-cve-2026-58041-check

Share

Offline Node.js evidence checker for CVE-2026-58041: SQLite cached iterator write replay. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
1224 days agoNot yet reviewed

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

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

node-cve-2026-58041-check

Offline version-evidence checker for CVE-2026-58041 — Node.js: SQLite cached iterator write replay.

The checker compares operator-reported Node.js runtime versions with the fixed releases in a dated rule snapshot (reviewed 2026-10-24). It never contacts websites, executes Node.js or project code, or sends exploit payloads, and there is no network mode. Hidden versions, custom builds, conflicting evidence, and uncovered branches remain unknown. A public URL is not an inventory.

Results are triage evidence, not a runtime assessment: every result has exploitability: not_tested, and no deployed-target assessment, runtime attestation or exploit verification is claimed.

  • Requirements · Quick start · Usage · Reported fixed versions
  • Interpreting results · Inventory formats · Output and provenance · Limits and exit codes
  • Documentation · Sources · Contributing · License

Synthetic report preview

Node.js synthetic report

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

Requirements

  • Python 3.10 or newer, standard library only. There are no runtime dependencies, and the executable node_cve_2026_58041_check.py can be copied alone.
  • An exact Node.js version obtained from the deployed process or container. The checker does not scan the current machine.

Quick start

python node_cve_2026_58041_check.py --version 24.18.1 --format json

Without --format, the report is CSV. Output goes to stdout unless --output is given.

Usage

# Several runtimes at once (each --version is a separate runtime)
python node_cve_2026_58041_check.py --version 24.18.1 --version 26.5.0 --format json
# JSON inventory to an HTML report file
python node_cve_2026_58041_check.py --inventory examples/inventory.example.json --format html --output report.html
# CSV inventory; exit 1 if any result is a finding
python node_cve_2026_58041_check.py --csv-list inventory.csv --fail-on-finding
# Help and local synthetic tests
python node_cve_2026_58041_check.py --help
python -m unittest -v

At least one of --version, --inventory or --csv-list is required. All three can be combined and each can be repeated; every --version value describes a separate runtime. JSON, CSV and HTML reports are built from the same evidence.

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. Default unknown, which is compared as upstream. upstream, official and official_upstream are also treated as upstream; any other value (such as a vendor name) yields vendor_build_unverified.
--sql-tag-store, --stale-iterator, --cached-statement-rebindingOperator observation (true or false) applied to the --version inputs. See Interpreting results.
--inventory FILEJSON object or array of entries. Repeatable.
--csv-list FILECSV with a node_version column. Repeatable.
--format csv|json|htmlReport format. Default csv.
--output FILEWrite the report to a new file instead of stdout. The directory must already exist.
--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 any result is potentially_affected or unsupported_runtime.
--tool-version, --helpPrint the tool version or the help text.

Existing report files are protected unless --force is explicit.

Reported fixed versions

Reviewed 2026-10-24 against the official release advisory and linked fixed releases. These are versions the vendor reports as fixed; the checker cannot verify that a given deployment actually runs them.

Node.js majorFixed version
24.x24.18.1
26.x26.5.1

How versions are classified:

  • The vendor does not establish an introduced version. Versions below the fixed version of a listed major are potentially_affected and require remediation.
  • Listed fix versions and later plain versions on that same major are fixed_version_reported.
  • Other active or future majors remain unknown; a newer or unlisted major is not assumed to be patched.
  • Old end-of-life majors produce unsupported_runtime as upgrade guidance, not as a claim that this particular flaw exists in every historical build. End-of-life is taken from the Node.js release schedule (https://raw.githubusercontent.com/nodejs/Release/main/schedule.json, reviewed 2026-10-24).
  • Prerelease, custom, backported and vendor builds need explicit vendor evidence and remain unknown. Do not label unknown builds safe.

Source conflict: Node.js 22.x

The sources disagree about Node.js 22.x, and the conflict is unresolved:

  • The nodejs.org July 2026 security releases page says the issue affects all users in active release lines 26.x and 24.x. 22.x is not named, although v22.23.2 is in the same release batch.
  • security-wg vuln/core/190.json lists vulnerable 24.x || 26.x and patched ^24.18.1 || ^26.5.1, but its overview text says it affects 22.x, 24.x and 26.x.
  • The CVE record (CVE-2026-58041 on cveawg.mitre.org) has the same 22.x, 24.x and 26.x text, with affected <=22.23.1, <=24.18.0 and <=26.5.0.

No 22.x fixed version is asserted for this CVE, so 22.x is deliberately not listed as affected or fixed and must stay unknown unless explicit evidence is obtained.

Interpreting results

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.

    806
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

    441
  • 4

    redforge

    cybersecurity91/redforge

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

    346
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    270
  • 6

    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.

    264

Explore all tools

Browse our collection of tools

View all tools →