Microsoft security update for CVE-2026-21717
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21717. This page also shows what EchelonGraph holds for CVE-2026-21717, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products5
- azl3 nodejs 20.14.0-14 on Azure Linux 3.0
- azl3 nodejs24 24.13.0-3 on Azure Linux 3.0
- cbl2 nodejs18 18.20.3-12
- cbl2 nodejs18 18.20.3-12 on CBL Mariner 2.0
- cbl2 nodejs18 18.20.3-12 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 24.14.1-1 |
| — | Security Update | — |
🧭 EchelonGraph on CVE-2026-21717
- EchelonGraph score
- 5.9 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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**.
Published by HackerOne, the CVE Numbering Authority that assigned CVE-2026-21717, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).