--- title: "Node.js — Wednesday, October 21, 2026 Security Releases" slug: node-js-wednesday-october-21-2026-security-releases url: https://listedarticles.com/articles/node-js-wednesday-october-21-2026-security-releases canonical_url: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases content_type: changelog language: en published_at: 2026-10-21T00:00:00.000Z updated_at: 2026-10-21T23:10:58.034Z author: "The Node.js Project" authored_by: human publisher: "Node.js" publisher_url: https://nodejs.org/ topics: ["Security", "JavaScript", "Open Source"] license: all-rights-reserved word_count: 646 reading_minutes: 3 citation: "The Node.js Project, Node.js. \"Node.js — Wednesday, October 21, 2026 Security Releases.\" 21 Oct 2026. https://nodejs.org/en/blog/vulnerability/october-2026-security-releases (all-rights-reserved)" # The full text follows. The web page shows an extract and sends readers # to the source above; quote the citation and link the canonical URL. --- # Node.js — Wednesday, October 21, 2026 Security Releases > The Node.js project ships security releases for the 26.x, 24.x and 22.x lines, updating c-ares, OpenSSL and the CA certificate store (removing the compromised eMudhra intermediate CA), with details of fixed issues and download links. # Wednesday, October 21, 2026 Security Releases The Node.js Project Wednesday, October 21, 2026 Security Releases ## [Security releases available](#security-releases-available) Updates are now available for the 26.x, 24.x, 22.x Node.js release lines for the following issues. This security release includes the following dependency updates to address public vulnerabilities: - c-ares on 26.x, 24.x, 22.x - ca-cert (eMudhra Intermediate CA Compromise) on 26.x, 24.x, 22.x - OpenSSL on 24.x, 22.x - SQLite on 22.x - Undici on 26.x, 24.x, 22.x ## [dns.resolve truncates names containing NUL char (CVE-2026-105482) - (high)](#dnsresolve-truncates-names-containing-nul-char-cve-2026-105482---high) This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. Thank you, to hasanfleyah for reporting this vulnerability and thank you jasnell for fixing it. ## [TLS certificate hostname bypass when the IP is written fullwidth digits (CVE-2026-105483) - (high)](#tls-certificate-hostname-bypass-when-the-ip-is-written-fullwidth-digits-cve-2026-105483---high) This vulnerability affects Node.js **26.x** and **24.x**. Thank you, to hasanfleyah for reporting this vulnerability and thank you jasnell for fixing it. ## [TLS certificate hostname bypass when the host loosely resolves to an IP address (CVE-2026-106069) - (high)](#tls-certificate-hostname-bypass-when-the-host-loosely-resolves-to-an-ip-address-cve-2026-106069---high) This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. Thank you, to anagnorisis2peripeteia for reporting this vulnerability and thank you mcollina for fixing it. ## [Node.js Brotli decoder out-of-bounds write permits remote code execution (CVE-2026-111497) - (high)](#nodejs-brotli-decoder-out-of-bounds-write-permits-remote-code-execution-cve-2026-111497---high) A flaw in Node.js can cause Node.js Brotli decoder out-of-bounds write permits remote code execution. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. Thank you, to mcollina for reporting this vulnerability and thank you aduh95 for fixing it. ## [Keep-alive socket process a response that was written before the request was sent (CVE-2026-105481) - (medium)](#keep-alive-socket-process-a-response-that-was-written-before-the-request-was-sent-cve-2026-105481---medium) This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. Thank you, to hasanfleyah for reporting this vulnerability and thank you jasnell for fixing it. ## [Improper certificate validation for non-canonical IPv4 hostnames allows DNS SANs to authenticate IP endpoints (CVE-2026-106072) - (medium)](#improper-certificate-validation-for-non-canonical-ipv4-hostnames-allows-dns-sans-to-authenticate-ip-endpoints-cve-2026-106072---medium) This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. Thank you, to br41ny for reporting this vulnerability and thank you mcollina for fixing it. ## [crypto.randomUUID() and randomInt() entropy caches are saved into user-land startup snapshots and SEAs, so every process repeats the same values (CVE-2026-106074) - (medium)](#cryptorandomuuid-and-randomint-entropy-caches-are-saved-into-user-land-startup-snapshots-and-seas-so-every-process-repeats-the-same-values-cve-2026-106074---medium) This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. Thank you, to gesposito for reporting this vulnerability and thank you panva for fixing it. ## [Node.js ZipFile returns attacker-controlled prefix bytes after failed ZIP header validation (CVE-2026-106070) - (low)](#nodejs-zipfile-returns-attacker-controlled-prefix-bytes-after-failed-zip-header-validation-cve-2026-106070---low) This vulnerability affects Node.js **26.x**. Thank you, to startimeash for reporting this vulnerability and thank you mcollina for fixing it. ## [Permission Model filesystem over-grant via wildcard radix lookup (CVE-2026-106071) - (low)](#permission-model-filesystem-over-grant-via-wildcard-radix-lookup-cve-2026-106071---low) This vulnerability affects Node.js **26.x**. Thank you, to malikhamzaiqbal for reporting this vulnerability and thank you jasnell for fixing it. ## [Permission Model bypass with fs.realpathSync (CVE-2026-106073) - (low)](#permission-model-bypass-with-fsrealpathsync-cve-2026-106073---low) This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. Thank you, to 0xoroot for reporting this vulnerability and thank you RafaelGSS for fixing it. ## [Downloads and release details](#downloads-and-release-details) - [Node.js v22.23.4](https://nodejs.org/en/blog/release/v22.23.4/) - [Node.js v24.22.1](https://nodejs.org/en/blog/release/v24.22.1/) - [Node.js v26.12.1](https://nodejs.org/en/blog/release/v26.12.1/) # [Summary](#summary) The Node.js project will release new versions of the 26.x, 24.x, 22.x releases lines on or shortly after, Wednesday, October 21, 2026 in order to address security vulnerabilities. The highest severity issue fixed in this release is HIGH. ## [Impact](#impact) - The highest severity issue fixed in the 26.x release line is HIGH. - The highest severity issue fixed in the 24.x release line is HIGH. - The highest severity issue fixed in the 22.x release line is HIGH. It's important to note that End-of-Life versions are always affected when a security release occurs. To ensure your system's security, please use an up-to-date version as outlined in our [Release Schedule](https://github.com/nodejs/release#release-schedule). ## [Release timing](#release-timing) Releases will be available on, or shortly after, Wednesday, October 21, 2026. ## [Contact and future updates](#contact-and-future-updates) The current Node.js security policy can be found at . Please follow the process outlined in if you wish to report a vulnerability in Node.js. Subscribe to the low-volume announcement-only nodejs-sec mailing list at to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the nodejs GitHub organization.