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-105483-check — Offline Node.js evidence checker for CVE-2026-105483: TLS fullwidth-IP hostname validation bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/node-cve-2026-105483-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingSupply Chain Security
GitHubcompletetech-security/node-cve-2026-105483-check

node-cve-2026-105483-check

Offline Node.js evidence checker for CVE-2026-105483: TLS fullwidth-IP hostname validation bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads.

Share
View RepositoryWebsite
124 days agoNot yet reviewed

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

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

node-cve-2026-105483-check

Offline evidence checker for CVE-2026-105483 — Node.js: TLS fullwidth-IP hostname validation bypass. It compares Node.js versions that you report against the fixed releases named in the official Node.js advisory. Python 3.10+, standard library only; the executable is a single file and can be copied on its own.

Scope. The checker compares operator-reported runtime versions. It never contacts websites, executes Node.js or project code, or sends exploit payloads, and it does not scan the current machine. Hidden versions, custom builds, conflicting evidence, and uncovered branches remain unknown. A public URL is not an inventory. No result is an exploit test, a deployed-patch attestation, or a production verification.

Contents

  • Quick start
  • Synthetic report preview
  • Fixed versions and version rules
  • Interpreting results
  • Inputs
  • Output formats
  • Limits, safety, and exit codes
  • Sources and provenance
  • Documentation, contributing, and license

Quick start

Requires Python 3.10 or newer and nothing else. Supply an exact version obtained from the deployed process (for example, from the running binary or container, not a workstation):

python node_cve_2026_105483_check.py --version 24.22.1 --format json
python node_cve_2026_105483_check.py --inventory examples/inventory.example.json --format html --output report.html
python node_cve_2026_105483_check.py --csv-list inventory.csv --fail-on-finding
python node_cve_2026_105483_check.py --help
python -m unittest -v
  • --version (alias --node-version) is repeatable; each value describes a separate runtime. A leading v is accepted.
  • --inventory FILE (JSON) and --csv-list FILE (CSV) are repeatable and can be combined with --version.
  • --format is csv (default), json, or html. Without --output, the report goes to stdout.
  • --build-source SOURCE states the provenance of the --version builds (default unknown, compared as upstream; upstream, official, or a vendor name).
  • --tls-client, --untrusted-nonascii-ip-host and --trusted-numeric-dns-certificate each take true or false and apply to every --version input. See Interpreting results.
  • --output FILE writes a new file. An existing report is protected unless --force is explicit, and an input file can never be overwritten, even with --force.
  • --brand NAME sets the organization name in the HTML report (default CompleteTech LLC, at most 512 characters).
  • --fail-on-finding makes potentially_affected and unsupported_runtime results exit 1.
  • --tool-version prints the tool name and version.

JSON, CSV and HTML reports are built from the same evidence. At least one of --version, --inventory or --csv-list is required.

Synthetic report preview

Node.js synthetic report

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

Fixed versions and version rules

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

Node.js majorFixed version
24.x24.22.1
26.x26.12.1

The vendor does not specify an introduced version in the release advisory. How a reported version is classified:

  • Below the fixed version of a listed major (24.x or 26.x): potentially_affected. These versions require remediation.
  • The fixed version or a later plain version on the same listed major: fixed_version_reported.
  • Old end-of-life majors: unsupported_runtime. This is upgrade guidance, not a claim that this particular flaw exists in every historical build. End-of-life status follows the Node.js release schedule reviewed 2026-10-24.
  • Other active or future majors not listed above: unknown; they are not assumed to be patched.
  • Prerelease, nightly, release-candidate, suffixed, or otherwise qualified versions, and unrecognized or partial versions: unknown; they need explicit evidence.
  • Vendor, distribution, backported, or custom builds (any --build-source or inventory build_source other than blank, unknown, upstream, official or official_upstream): unknown. They need vendor evidence, because fixes may be backported and the upstream version does not show which patches a build contains.
  • Missing or conflicting versions: unknown. Missing metadata does not establish that a runtime is unaffected.

Unknown builds must never be labeled safe.

Interpreting results

statusMeaning
potentially_affectedThe reported version is below the fixed release of its major and needs remediation review.
fixed_version_reportedThe reported version is at or above the fixed release. This is not deployed-patch attestation: confirm that the running process or container actually uses that release, not only a patched workstation or lockfile.
unsupported_runtimeThe major is past end-of-life. Upgrade guidance, not proof that the flaw is present.
unknownMissing, conflicting, qualified, vendor/custom-build, or uncovered evidence.

Each result also carries a more specific version_status (for example below_fixed_version, at_or_above_fixed_version, unsupported_release_line, release_line_not_in_rules, qualified_version_unverified, vendor_build_unverified, conflicting_versions, unrecognized_or_partial_version, version_not_disclosed).

Every result has exploitability: not_tested. A reported fixed version is not a verified deployed patch, and a potentially_affected result is not evidence of actual exploitation.

Operator-supplied preconditions are recorded separately as reported_true, reported_false, or not_reported. They are unverified, never change the version result, and do not establish reachability.

Precondition observationMeaning
tls_clienttls client
untrusted_nonascii_ip_hostuntrusted nonascii ip host
trusted_numeric_dns_certificatetrusted numeric dns certificate

Inputs

All input files must be regular UTF-8 files. Use stable local copies.

JSON inventory (--inventory) is one object or an array. See examples/inventory.example.json.

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.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

    385
  • 4

    redforge

    cybersecurity91/redforge

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

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

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

    279

Explore all tools

Browse our collection of tools

View all tools →