CVE-2026-21717: nodejs vulnerability
nodejs · node
Vendor fix available · Affected: nodejs · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 19% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- nodejs · nodefrom 20.20.1 up to and including 20.20.1; from 22.22.1 up to and including 22.22.1; from 24.14.0 up to and including 24.14.0; from 25.8.1 up to and including 25.8.1; from 4.0 before 4.*; from 5.0 before 5.* and 14 more
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Use of Weak Hash · Cryptography
- Vendor
- nodejs
- Published
- March 2026
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2026-21717
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- HashDoS in V8Node.js · 2026 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2026-21717 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.