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-58042-check — Offline Node.js evidence checker for CVE-2026-58042: DNS resolveAny process abort. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/node-cve-2026-58042-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingUtilities & FrameworksIncident Response
GitHubcompletetech-security/node-cve-2026-58042-check

node-cve-2026-58042-check

Share

Offline Node.js evidence checker for CVE-2026-58042: DNS resolveAny process abort. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
1224 days agoNot yet reviewed

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

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

node-cve-2026-58042-check

Offline evidence checker for CVE-2026-58042 — Node.js: DNS resolveAny process abort.

It compares Node.js versions that you report against the fixed releases named in the vendor advisory and writes a CSV, JSON or HTML report. Python 3.10+, standard library only; the single executable can be copied on its own.

  • Version evidence only. It never contacts websites, runs Node.js or project code, or sends exploit payloads. There is no network mode and no automatic scan of the current machine.
  • Conservative by design. Hidden versions, custom or vendor builds, conflicting evidence and uncovered release lines stay unknown. A public URL is not an inventory.
  • No exploit verification. Every result carries exploitability: not_tested. A reported fixed version is not proof that the deployed runtime is patched.

Contents

  • Quick start
  • Report preview
  • Fixed versions and classification
  • Interpreting results
  • Usage
  • Input formats
  • Output and publication
  • Limits and exit codes
  • Report provenance
  • Handling inventories and reports
  • Sources
  • Further reading, contributing and license

Quick start

Requirements: Python 3.10 or newer. No packages to install.

python node_cve_2026_58042_check.py --version 22.23.2 --format json
python node_cve_2026_58042_check.py --inventory examples/inventory.example.json --format html --output report.html
python node_cve_2026_58042_check.py --csv-list inventory.csv --fail-on-finding
python node_cve_2026_58042_check.py --help
python -m unittest -v

Supply the version of the executable actually used by the serving process. A different node on the host or container PATH may report another version; a package upgrade alone does not establish that an already-running process restarted with it. --version is repeatable; each value describes a separate runtime. The default output format is CSV on stdout.

Report preview

Node.js synthetic report

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

Fixed versions and classification

Reviewed 2026-10-24 against the official release advisory and the linked fixed releases.

Node.js majorFixed version
22.x22.23.2
24.x24.18.1
26.x26.5.1

For each listed major, versions below its fixed version require remediation. The vendor does not specify an introduced version in the release advisory, so every earlier version on a listed major is treated as possibly affected.

Reported versionResult
Plain version on a listed major, below the fixed versionpotentially_affected
Fixed version, or a later plain version on the same listed majorfixed_version_reported
Plain version on an end-of-life majorunsupported_runtime
Any other active or future majorunknown (release_line_not_in_rules)
Missing, malformed, conflicting, prerelease, nightly/rc, suffixed or otherwise qualified versionunknown
Vendor, distribution, custom or unrecognized build_sourceunknown (vendor_build_unverified)
  • unsupported_runtime is upgrade guidance, not a claim that this particular flaw exists in every historical build. The end-of-life majors are taken from the Node.js release schedule, reviewed 2026-10-24 (the 0.x series is an inference from that schedule).
  • Vendor, backported and custom builds need vendor evidence, because the upstream version does not show which patches they contain. Unlisted, custom/backported and prerelease builds need explicit evidence; do not label unknown builds safe.
  • Build source is checked before the version: only unknown (the default), upstream, official, official_upstream or blank are compared as upstream builds.
  • A leading v and surrounding ASCII whitespace are ignored; anything else beyond MAJOR.MINOR.PATCH makes the version qualified.

Interpreting results

StatusMeaning
potentially_affectedThe reported version is below the fixed release of its major and needs remediation review. This is not confirmed exploitability.
fixed_version_reportedThe reported version is at or above the fixed release. This is not deployed-patch attestation: confirm the running process or container actually uses that release, not only a workstation or lockfile.
unsupported_runtimeThe major is past end of life. Migrate to a supported, fixed release.
unknownEvidence is missing or unclassifiable. Collect the exact upstream version and build provenance of the running process and run the checker again.

Each result also carries a more specific version_status (such as below_fixed_version, at_or_above_fixed_version, unsupported_release_line, release_line_not_in_rules, version_not_disclosed, qualified_version_unverified, unrecognized_or_partial_version or vendor_build_unverified), the applicable fixed_version, a recommendation, and notes. evidence_type is operator_reported_version; evidence_confidence is low, or insufficient for unknown.

Exploitability is never tested. Optional precondition observations are operator-supplied and unverified; they are recorded separately, never change the version result, and do not establish reachability.

Observation keyMeaning
dns_resolve_anydns resolve any
untrusted_dns_responsesuntrusted dns responses

Each observation is reported as reported_true, reported_false or not_reported.

Usage

python node_cve_2026_58042_check.py [options]

At least one of --version, --inventory or --csv-list is required. Run --help for the authoritative option list.

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.

    851
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

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

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

    280

Explore all tools

Browse our collection of tools

View all tools →