Linux · Amazon Linux · Security advisory · April 13, 2026

ALAS2023-2026-1576: Security update for 10 packages

ALAS2023-2026-1576, released April 13, 2026, fixes 6 CVEs across 10 products. None of them is reported as exploited. Patch Radar priority: High.

High
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
7.5
Base score, 0 to 10
Highest EPSS
0.2544
97th percentile

Priority of the 6 CVEs

Patch now 0 Urgent 0 High 6 Routine 0

Fixed package versions

ProductReleaseFixed in
nodejs22amzn 20231:22.22.2-1.amzn2023.0.1
nodejs22-debuginfoamzn 20231:22.22.2-1.amzn2023.0.1
nodejs22-debugsourceamzn 20231:22.22.2-1.amzn2023.0.1
nodejs22-develamzn 20231:22.22.2-1.amzn2023.0.1
nodejs22-docsamzn 20231:22.22.2-1.amzn2023.0.1
nodejs22-full-i18namzn 20231:22.22.2-1.amzn2023.0.1
nodejs22-libsamzn 20231:22.22.2-1.amzn2023.0.1
nodejs22-libs-debuginfoamzn 20231:22.22.2-1.amzn2023.0.1
nodejs22-npmamzn 20231:10.9.7-1.22.22.2.1.amzn2023.0.1
v8-12.4-develamzn 20233:12.4.254.21-1.22.22.2.1.amzn2023.0.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
High CVE-2026-21710 A 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**7.5 0.2544 None reported
High CVE-2026-21714 Node.js 14 and 15 others: Missing Release of Memory after Effective Lifetime7.5 0.0043 None reported
High CVE-2026-21713 Node.js 14 and 15 others: Observable Timing Discrepancy7.5 0.0037 None reported
High CVE-2026-21717 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**.7.5 0.0027 None reported
High CVE-2026-21715 Node.js 14 and 15 others: Incorrect Permission Assignment for Critical Resource7.5 0.0015 None reported
High CVE-2026-21716 Node.js 14 and 15 others: Missing Authorization7.5 0.0014 None reported
Showing 1 to 6 of 6 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.