{
  "product": "Node.js 14",
  "url": "https://patchblox.com/security/product/windows-app/node.js-14",
  "summary": "The latest version of Node.js 14 is 14.21.3, released February 16, 2023. Patch Radar has 16 security fixes for Node.js 14, closing 34 CVEs. The newest security fix is Node.js 14 14.21.3, released February 16, 2023. 11 CVEs have no fix yet.",
  "platform": "windows-app",
  "vendor": "Node.js Foundation",
  "supported": true,
  "latestVersion": "14.21.3",
  "latestReleased": "2023-02-16T00:00:00Z",
  "fixCount": 16,
  "cveCount": 34,
  "exploitedCveCount": 0,
  "unfixedCveCount": 11,
  "fixes": [
    {
      "fix": "Node.js 14 14.21.3",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.21.3",
      "released": "2023-02-16T00:00:00Z",
      "fixedVersion": "14.21.3",
      "priority": "High",
      "cveCount": 3,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.21.1",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.21.1",
      "released": "2022-11-04T00:00:00Z",
      "fixedVersion": "14.21.1",
      "priority": "High",
      "cveCount": 1,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.20.1",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.20.1",
      "released": "2022-09-23T00:00:00Z",
      "fixedVersion": "14.20.1",
      "priority": "High",
      "cveCount": 3,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.20.0",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.20.0",
      "released": "2022-07-07T00:00:00Z",
      "fixedVersion": "14.20.0",
      "priority": "High",
      "cveCount": 3,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.18.3",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.18.3",
      "released": "2022-01-10T00:00:00Z",
      "fixedVersion": "14.18.3",
      "priority": "High",
      "cveCount": 4,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.18.1",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.18.1",
      "released": "2021-10-12T00:00:00Z",
      "fixedVersion": "14.18.1",
      "priority": "High",
      "cveCount": 2,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.17.5",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.17.5",
      "released": "2021-08-11T00:00:00Z",
      "fixedVersion": "14.17.5",
      "priority": "High",
      "cveCount": 4,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.17.4",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.17.4",
      "released": "2021-07-29T00:00:00Z",
      "fixedVersion": "14.17.4",
      "priority": "High",
      "cveCount": 1,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.17.2",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.17.2",
      "released": "2021-07-01T00:00:00Z",
      "fixedVersion": "14.17.2",
      "priority": "High",
      "cveCount": 2,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.16.0",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.16.0",
      "released": "2021-02-23T00:00:00Z",
      "fixedVersion": "14.16.0",
      "priority": "High",
      "cveCount": 2,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.15.4",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.15.4",
      "released": "2021-01-04T00:00:00Z",
      "fixedVersion": "14.15.4",
      "priority": "High",
      "cveCount": 2,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.15.1",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.15.1",
      "released": "2020-11-16T00:00:00Z",
      "fixedVersion": "14.15.1",
      "priority": "High",
      "cveCount": 1,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.11.0",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.11.0",
      "released": "2020-09-15T00:00:00Z",
      "fixedVersion": "14.11.0",
      "priority": "High",
      "cveCount": 2,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.9.0",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.9.0",
      "released": "2020-08-27T00:00:00Z",
      "fixedVersion": "14.9.0",
      "priority": "High",
      "cveCount": 1,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.5.0",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.5.0",
      "released": "2020-06-30T00:00:00Z",
      "fixedVersion": "14.5.0",
      "priority": "High",
      "cveCount": 1,
      "exploitedCveCount": 0
    },
    {
      "fix": "Node.js 14 14.4.0",
      "url": "https://patchblox.com/security/fix/windows-app/openjs.nodejs.14-14.4.0",
      "released": "2020-06-02T00:00:00Z",
      "fixedVersion": "14.4.0",
      "priority": "High",
      "cveCount": 2,
      "exploitedCveCount": 0
    }
  ],
  "noFixYet": [
    {
      "cveId": "CVE-2024-3566",
      "url": "https://patchblox.com/security/cve/CVE-2024-3566",
      "title": "Command injection vulnerability in programing languages on Microsoft Windows operating system.",
      "priority": "Urgent",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-106071",
      "url": "https://patchblox.com/security/cve/CVE-2026-106071",
      "title": "A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard \u0060--allow-fs-read\u0060 or \u0060--allow-fs-write\u0060 rule.\n\nWhen 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, \u0060--allow-fs-read=/etc/passwd.*\u0060 also allows reading \u0060/etc/passwd\u0060. 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.\n\nThis vulnerability affects Node.js **26.x**.",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-21637",
      "url": "https://patchblox.com/security/cve/CVE-2026-21637",
      "title": "HackerOne: CVE-2026-21637 TLS PSK/ALPN Callback Exceptions Bypass Error Handlers",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-21710",
      "url": "https://patchblox.com/security/cve/CVE-2026-21710",
      "title": "A flaw in Node.js HTTP request handling causes an uncaught \u0060TypeError\u0060 when a request is received with a header named \u0060__proto__\u0060 and the application accesses \u0060req.headersDistinct\u0060.\n\nWhen this occurs, \u0060dest[\u0022__proto__\u0022]\u0060 resolves to \u0060Object.prototype\u0060 rather than \u0060undefined\u0060, causing \u0060.push()\u0060 to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by \u0060error\u0060 event listeners, meaning it cannot be handled without wrapping every \u0060req.headersDistinct\u0060 access in a \u0060try/catch\u0060.\n\n* This vulnerability affects all Node.js HTTP servers on **20.x, 22.x, 24.x, and v25.x**",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-21711",
      "url": "https://patchblox.com/security/cve/CVE-2026-21711",
      "title": "Node.js 14 and 12 others: Improper Access Control",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-21713",
      "url": "https://patchblox.com/security/cve/CVE-2026-21713",
      "title": "Node.js 14 and 15 others: Observable Timing Discrepancy",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-21714",
      "url": "https://patchblox.com/security/cve/CVE-2026-21714",
      "title": "Node.js 14 and 15 others: Missing Release of Memory after Effective Lifetime",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-21715",
      "url": "https://patchblox.com/security/cve/CVE-2026-21715",
      "title": "Node.js 14 and 15 others: Incorrect Permission Assignment for Critical Resource",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-21716",
      "url": "https://patchblox.com/security/cve/CVE-2026-21716",
      "title": "Node.js 14 and 15 others: Missing Authorization",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-21717",
      "url": "https://patchblox.com/security/cve/CVE-2026-21717",
      "title": "A flaw in V8\u0027s 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\u0027s internal string table, an attacker can significantly degrade performance of the Node.js process.\n\nThe most common trigger is any endpoint that calls \u0060JSON.parse()\u0060 on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table.\n\nThis vulnerability affects **20.x, 22.x, 24.x, and 25.x**.",
      "priority": "High",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    },
    {
      "cveId": "CVE-2026-106070",
      "url": "https://patchblox.com/security/cve/CVE-2026-106070",
      "title": "Node.js and 17 others: Business Logic Errors",
      "priority": "Routine",
      "status": "no-fix",
      "affectedVersion": "14.21.3"
    }
  ],
  "dataAsOf": "2026-11-07T18:46:35Z"
}