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
CVE-2026-21717 — Proof-of-concept for CVE-2026-21717, a Node.js V8 string hashing collision vulnerability causing denial of service via crafted JSON payloads. | Kitploit
Tools/GitHubGitHub/open-flaw/cve-2026-21717
Vulnerability AnalysisExploitationLearning & Education
GitHubopen-flaw/cve-2026-21717

CVE-2026-21717

Proof-of-concept for CVE-2026-21717, a Node.js V8 string hashing collision vulnerability causing denial of service via crafted JSON payloads.

View Repository
257 months agoNot yet reviewed

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.

    916
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    707
  • 3

    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.

    430
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    402
  • 5

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    349
  • 6

    ARTEX

    baarai/artex

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

    341

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-21717

Node.js V8 String Hashing Predictable Collision Vulnerability Leading to Denial of Service

Overview

A critical vulnerability in V8's string hashing mechanism allows attackers to cause severe performance degradation in Node.js applications. Integer-like strings are hashed to their numeric value, making hash collisions trivially predictable. By crafting malicious input that causes many collisions in V8's internal string table, an attacker can significantly degrade performance or cause a denial of service.

Vulnerability Details

  • CVE ID: CVE-2026-21717
  • Severity: High
  • Attack Vector: Network
  • Attack Complexity: Low
  • Impact: Denial of Service (DoS)

Technical Description

The vulnerability stems from V8's string internalization process. When JSON parsing occurs, short strings are automatically internalized into a hash table. Integer-like strings collide predictably because they hash to their numeric values, allowing attackers to force quadratic probing chains that severely degrade performance.

Affected Components

The most common trigger is any endpoint that calls JSON.parse() on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table.

Proof of Concept

This repository contains a proof-of-concept demonstrating the vulnerability:

Prerequisites

# Use Node.js version affected by CVE-2026-21717
nvm use
npm install

Running the PoC

node poc.js

Expected Behavior

The PoC creates a payload with:

  • A quadratic probing chain of ~130k strings
  • Repeated target values forcing lookups through the chain
  • Results in ~44+ seconds of CPU time for a single JSON.parse() operation

Attack Flow

  1. Attacker crafts an adversarial JSON payload containing integer-like strings designed to collide
  2. Client sends the malicious JSON to the server
  3. Server calls JSON.parse() on the untrusted input
  4. V8 Engine internalizes strings into hash table, triggering collisions
  5. Result Extreme CPU consumption and performance degradation

Mitigation

Recommended Actions

  1. Update Node.js to a patched version that addresses this vulnerability
  2. Input Validation: Limit the size and complexity of JSON payloads
  3. Rate Limiting: Implement rate limiting on endpoints accepting JSON input
  4. Timeouts: Set reasonable timeouts for JSON parsing operations
  5. Resource Monitoring: Monitor CPU usage for abnormal spikes

Code-Level Mitigations

// Limit payload size
app.use(express.json({ limit: '100kb' }));

// Add timeout for parsing
const parseWithTimeout = (str, timeout = 1000) => {
  return Promise.race([
    Promise.resolve(JSON.parse(str)),
    new Promise((_, reject) => 
      setTimeout(() => reject(new Error('Parse timeout')), timeout)
    )
  ]);
};

References

  • CVE Details
  • Node.js Security Blog

Disclaimer

This repository is for educational and research purposes only. Do not use this code for malicious purposes or against systems you do not own or have explicit permission to test.

Download Tool