critical CVSS 9 EPSS 0.27%

CVE-2026-21717·Node.js vulnerability

A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade performance of the Node.js process. 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. This vulnerability affects **20.x, 22.x, 24.x, and 25.x**.

Severity
critical
Software
Node.js
Fixed in
20.19.2+dfsg-1+deb13u2
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.27% — higher than 17% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2026-21717 scores 9 on CVSS, so a successful attack would be serious — but at 0.27%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 20.19.2+dfsg-1+deb13u2

Fixed in: 20.19.2+dfsg-1+deb13u2

How to fix this CVE

Update Node.js to version 20.19.2 or later to patch the V8 string hashing vulnerability that enables denial-of-service attacks through hash collision exploitation. Organizations running Node.js 20.x, 22.x, 24.x, or 25.x should prioritize this update, particularly for services that parse untrusted JSON data. After patching, restart all affected Node.js processes to ensure the fixed version is running.

sudo dnf update nodejs

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|PUT|PATCH requests with JSON payloads containing repeated numeric string keys (e.g., {"123":..., "456":..., "789":...}) targeting JSON parsing endpoints, often followed by sustained high CPU usage or response timeouts

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch.

Implement request rate limiting on JSON parsing endpoints and consider payload size restrictions. Add WAF rules to detect and reject JSON payloads with excessive repetition of numeric string patterns that do not match legitimate application schemas.

How to check if you are affected

  1. Check installed Node.js version with: node --version or nodejs --version
  2. Identify exposed JSON parsing endpoints by reviewing application code for JSON.parse() calls on request bodies, query parameters, or file uploads
  3. Search application logs for unusual patterns of repeated failed requests or POST/PUT operations with similar payloads targeting JSON endpoints
  4. After patching, verify the fix with: node --version and confirm it reports 20.19.2 or later, then monitor CPU usage during JSON parsing to confirm performance normalization

FAQ

What is CVE-2026-21717?

This vulnerability exploits a flaw in V8's string hashing that allows attackers to craft malicious JSON payloads triggering predictable hash collisions, causing the Node.js process to consume excessive CPU resources and become unresponsive.

Is CVE-2026-21717 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits have been disclosed, though the attack pattern is straightforward.

What versions of Node.js are affected by CVE-2026-21717?

Node.js versions 20.x (before 20.19.2), 22.x, 24.x, and 25.x are affected. Version 20.19.2 and later contain the fix.

How do I check if my server is vulnerable to CVE-2026-21717?

Run node --version and compare against 20.19.2. If your version is 20.19.1 or earlier, or any version in the 22.x, 24.x, or 25.x ranges, you are vulnerable.

Does Defensia detect CVE-2026-21717?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Node.js is installed on a monitored server, CVE-2026-21717 will appear in your dashboard with remediation steps.

Related Node.js CVEs

CVE-2026-21636CVSS 10A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when `--permission` is enabled. Even without `--allow-net`, attacker-controlled inputs (such as URLs or socketPath options) can connect to arbitrary local sockets via net, tls, or undici/fetch. This breaks the intended security boundary of the permission model and enables access to privileged local services, potentially leading to privilege escalation, data exposure, or local code execution. * The issue affects users of the Node.js permission model on version v25. In the moment of this vulnerability, network permissions (`--allow-net`) are still in the experimental phase.
CVE-2026-111497CVSS 9.8A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1.2.1.
CVE-2026-48930CVSS 9.8A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2025-55130CVSS 9.1A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.
CVE-2026-21710CVSS 9A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the application accesses `req.headersDistinct`. When this occurs, `dest["__proto__"]` resolves to `Object.prototype` rather than `undefined`, causing `.push()` to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by `error` event listeners, meaning it cannot be handled without wrapping every `req.headersDistinct` access in a `try/catch`. * This vulnerability affects all Node.js HTTP servers on **20.x, 22.x, 24.x, and v25.x**

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-21717. Free for 1 server.

Get started free