Windows apps · Node.js Foundation
Node.js 12 security updates
The latest version of Node.js 12 is 12.22.12, released April 5, 2022. Patch Radar has 8 security fixes for Node.js 12, closing 18 CVEs. The newest security fix is Node.js 12 12.22.9, released January 10, 2022. Version 12.22.12 adds no new CVE fixes and includes all of them. 11 CVEs have no fix yet.
11 with no fix yet
Latest version
12.22.12
Released Apr 5, 2022
Security fixes
8
On record in Patch Radar
CVEs
18
Closed by those fixes
Exploited
0
Vendor report or CISA KEV
CVEs with no fix yet
| Priority | CVE | Title | Status |
|---|---|---|---|
| Urgent | CVE-2024-3566 | Command injection vulnerability in programing languages on Microsoft Windows operating system. | no-fix |
| High | CVE-2026-106071 | A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard `--allow-fs-read` or `--allow-fs-write` rule. When the requested path is shorter than the prefix of a wildcard grant, the radix tree lookup stops comparing early and treats the path as a match. For example, `--allow-fs-read=/etc/passwd.*` also allows reading `/etc/passwd`. This requires the wildcard grant to sit directly under the root of the permission tree, for example when it is the only grant for that scope. This is a different root cause from CVE-2026-58043. This vulnerability affects Node.js **26.x**. | no-fix |
| High | CVE-2026-21637 | HackerOne: CVE-2026-21637 TLS PSK/ALPN Callback Exceptions Bypass Error Handlers | no-fix |
| 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** | no-fix |
| High | CVE-2026-21711 | Node.js 14 and 12 others: Improper Access Control | no-fix |
| High | CVE-2026-21713 | Node.js 14 and 15 others: Observable Timing Discrepancy | no-fix |
| High | CVE-2026-21714 | Node.js 14 and 15 others: Missing Release of Memory after Effective Lifetime | no-fix |
| High | CVE-2026-21715 | Node.js 14 and 15 others: Incorrect Permission Assignment for Critical Resource | no-fix |
| High | CVE-2026-21716 | Node.js 14 and 15 others: Missing Authorization | no-fix |
| 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**. | no-fix |
| Routine | CVE-2026-106070 | Node.js and 17 others: Business Logic Errors | no-fix |
Security fixes, newest first
| Priority | Fix | Fixed in | CVEs | Exploited | Released |
|---|---|---|---|---|---|
| Latest | Node.js 12 12.22.12 | 12.22.12 | Includes every fix below | Apr 5, 2022 | |
| High | Node.js 12 12.22.9 | 12.22.9 | 4 | Jan 10, 2022 | |
| High | Node.js 12 12.22.7 | 12.22.7 | 2 | Oct 12, 2021 | |
| High | Node.js 12 12.22.5 | 12.22.5 | 4 | Aug 11, 2021 | |
| High | Node.js 12 12.22.4 | 12.22.4 | 1 | Jul 29, 2021 | |
| High | Node.js 12 12.22.2 | 12.22.2 | 2 | Jul 1, 2021 | |
| High | Node.js 12 12.21.0 | 12.21.0 | 2 | Feb 23, 2021 | |
| High | Node.js 12 12.20.1 | 12.20.1 | 2 | Jan 4, 2021 | |
| High | Node.js 12 12.20.0 | 12.20.0 | 1 | Nov 24, 2020 | |
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.