CVE-2026-21717

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2026-03-30. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
20.2%
KEV
Not listed

Published

March 30, 2026

Last Modified

May 10, 2026

Advisory Details (1)

Auto-updated May 10, 2026
No patch confirmed yet.
generic

Node.js — Tuesday, March 24, 2026 Security Releases

https://nodejs.org/en/blog/vulnerability/march-2026-security-releases

Vendor Advisories for CVE-2026-21717(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs24-1:24.14.1-2.el10_12026-04-13redhat
redhatnodejs:24-8100020260408131901.6d8804032026-04-13redhat
redhatnodejs22-main-22.22.0-1.3.hum12026-04-10redhat
redhatnodejs20-main-20.20.0-7.1.hum12026-04-10redhat
redhatnodejs:24-9070020260402152654.rhel92026-04-09redhat
redhatnodejs25-main-25.9.0-1.hum12026-04-02redhat
redhatnodejs24-main-24.14.1-4.hum12026-04-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 106 total refreshes for this CVE.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-08 15:15 UTCEPSS rescore
  6. 2026-07-08 15:15 UTCEPSS rescore
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-01 15:06 UTCEPSS rescore
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 75 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 01:59 UTCEPSS rescore
  6. 2026-06-21 01:59 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-17 17:53 UTCEPSS rescore
  10. 2026-06-16 17:52 UTCEPSS rescore
  11. 2026-06-15 17:48 UTCEPSS rescore
  12. 2026-06-14 23:18 UTCEPSS rescore
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-13 23:00 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-11 22:46 UTCEG score recompute
  17. 2026-06-11 22:46 UTCVendor advisory
  18. 2026-06-11 22:46 UTCGHSA enrichment
  19. 2026-06-11 14:00 UTCEPSS rescore
  20. 2026-06-10 22:18 UTCEPSS rescore
  21. 2026-06-10 15:36 UTCEG score recompute
  22. 2026-06-10 15:36 UTCVendor advisory
  23. 2026-06-10 15:36 UTCGHSA enrichment
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-09 15:13 UTCEG score recompute
  26. 2026-06-09 15:13 UTCVendor advisory
  27. 2026-06-09 15:13 UTCGHSA enrichment
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 14:17 UTCEPSS rescore
  30. 2026-06-08 13:05 UTCEG score recompute
  31. 2026-06-08 13:05 UTCVendor advisory
  32. 2026-06-08 13:05 UTCGHSA enrichment
  33. 2026-06-07 15:25 UTCEPSS rescore
  34. 2026-06-07 15:24 UTCEPSS rescore
  35. 2026-06-07 11:42 UTCEG score recompute
  36. 2026-06-07 11:42 UTCVendor advisory
  37. 2026-06-07 11:42 UTCGHSA enrichment
  38. 2026-06-06 13:47 UTCEPSS rescore
  39. 2026-06-06 13:47 UTCEPSS rescore
  40. 2026-06-06 13:47 UTCEPSS rescore
  41. 2026-06-05 22:47 UTCEPSS rescore
  42. 2026-06-05 06:10 UTCEPSS rescore
  43. 2026-06-05 06:10 UTCEPSS rescore
  44. 2026-06-04 13:12 UTCEPSS rescore
  45. 2026-06-04 13:12 UTCEPSS rescore
  46. 2026-06-04 13:12 UTCEPSS rescore
  47. 2026-06-02 20:13 UTCEPSS rescore
  48. 2026-06-02 20:13 UTCEPSS rescore
  49. 2026-06-01 13:51 UTCEPSS rescore
  50. 2026-06-01 13:51 UTCEPSS rescore
  51. 2026-06-01 13:51 UTCEPSS rescore
  52. 2026-05-31 22:30 UTCEPSS rescore
  53. 2026-05-31 22:30 UTCEPSS rescore
  54. 2026-05-31 00:16 UTCEPSS rescore
  55. 2026-05-31 00:16 UTCEPSS rescore
  56. 2026-05-31 00:16 UTCEPSS rescore
  57. 2026-05-29 13:44 UTCEPSS rescore
  58. 2026-05-29 13:44 UTCEPSS rescore
  59. 2026-05-28 13:44 UTCEPSS rescore
  60. 2026-05-28 13:44 UTCEPSS rescore
  61. 2026-05-28 13:44 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-27 13:40 UTCEPSS rescore
  64. 2026-05-27 13:40 UTCEPSS rescore
  65. 2026-05-26 13:44 UTCEPSS rescore
  66. 2026-05-26 13:44 UTCEPSS rescore
  67. 2026-05-26 07:18 UTCEPSS rescore
  68. 2026-05-26 07:18 UTCEPSS rescore
  69. 2026-05-26 07:18 UTCEPSS rescore
  70. 2026-05-22 21:16 UTCEPSS rescore
  71. 2026-05-21 22:43 UTCEPSS rescore
  72. 2026-05-20 22:38 UTCEPSS rescore
  73. 2026-05-20 22:37 UTCEPSS rescore
  74. 2026-05-20 22:37 UTCEPSS rescore
  75. 2026-05-20 19:54 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-21717?
CVE-2026-21717 is a medium vulnerability published on March 30, 2026. 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…
When was CVE-2026-21717 disclosed?
CVE-2026-21717 was first published in the National Vulnerability Database on March 30, 2026, with the most recent update on May 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21717 actively exploited?
CVE-2026-21717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-21717?
CVE-2026-21717 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-21717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21717, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-21717

Explore →

Is Your Infrastructure Affected by CVE-2026-21717?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs