CVE-2026-21717: Vulnerability in nodejs node
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**.
AI Analysis
Technical Summary
This vulnerability arises from a flaw in the V8 JavaScript engine's string hashing mechanism used by Node.js. Integer-like strings are hashed to their numeric values, making hash collisions trivially predictable. An attacker can craft input that triggers many such collisions in V8's internal string table, causing significant performance degradation of the Node.js process. The issue is especially relevant for endpoints that parse JSON from attacker-controlled input, as JSON.parse() internalizes short strings into the vulnerable hash table. Affected Node.js versions include 20.x, 22.x, 24.x, 25.x, and earlier major versions. The CVSS 3.0 score is 5.9 with vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating network attack vector with high attack complexity and no privileges or user interaction required, impacting availability only. No patch or remediation details are currently provided.
Potential Impact
The vulnerability allows an attacker to cause significant performance degradation of the Node.js process by triggering predictable hash collisions in V8's internal string table. This results in a denial-of-service-like condition affecting availability. There is no impact on confidentiality or integrity. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider limiting or validating attacker-controlled input that is parsed via JSON.parse() to reduce exposure. Monitor vendor channels for updates and patches addressing this vulnerability.
CVE-2026-21717: Vulnerability in nodejs node
Description
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**.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from a flaw in the V8 JavaScript engine's string hashing mechanism used by Node.js. Integer-like strings are hashed to their numeric values, making hash collisions trivially predictable. An attacker can craft input that triggers many such collisions in V8's internal string table, causing significant performance degradation of the Node.js process. The issue is especially relevant for endpoints that parse JSON from attacker-controlled input, as JSON.parse() internalizes short strings into the vulnerable hash table. Affected Node.js versions include 20.x, 22.x, 24.x, 25.x, and earlier major versions. The CVSS 3.0 score is 5.9 with vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating network attack vector with high attack complexity and no privileges or user interaction required, impacting availability only. No patch or remediation details are currently provided.
Potential Impact
The vulnerability allows an attacker to cause significant performance degradation of the Node.js process by triggering predictable hash collisions in V8's internal string table. This results in a denial-of-service-like condition affecting availability. There is no impact on confidentiality or integrity. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider limiting or validating attacker-controlled input that is parsed via JSON.parse() to reduce exposure. Monitor vendor channels for updates and patches addressing this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-01-04T15:00:06.575Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 69cacda7e6bfc5ba1d6188b4
Added to database: 3/30/2026, 7:23:19 PM
Last enriched: 5/11/2026, 1:44:53 AM
Last updated: 5/14/2026, 11:58:14 PM
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.