See how openjs foundation compares to other vendors in security performance
CISA added CVE-2026-111497, a Brotli decompression memory-corruption vulnerability, to its Known Exploited Vulnerabilities catalog. It can potentially enable information disclosure, crashes, or remote code execution in affected applications.
Node.js, .NET, and other software using vulnerable Brotli decoders may be exposed when processing attacker-controlled compressed data.
Apply relevant patches and redeploy affected applications or containers. CISA's listing confirms exploitation, but doesn't establish widespread successful production compromises.
On 10/14/26 09:36, Antoine du Hamel wrote: Security release pre-alert:
We will release new versions of Node.js 22, 24, and 26 release lines on or shortly after 2026-10-21 in order to address security vulnerabilities, the highest being HIGH.
https://nodejs.org/en/blog/vulnerability/october-2026-security-releases I didn't see a followup, but these releases are out now, and the above URL lists: 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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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. -- -Alan Coopersmith- alan.coopersmith () oracle com Oracle Solaris Engineering - https://blogs.oracle.com/solaris
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
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:
undici (8.9.0, 7.29.0, 6.28.0) on 26.x, 24.x, 22.x
llhttp (9.4.3) on 26.x, 24.x, 22.x
An incomplete fix for CVE-2026-48934 has been identified in Node.js. HTTPS Agent TLS session reuse can skip hostname verification across identity policies.
A flaw in node:sqlite allows a stale StatementSyncIterator created through DatabaseSync#createTagStore() to continue executing a cached prepared statement after it has been reset and rebound with new parameters. SQLTagStore resets cached statements using sqlite3reset() directly, bypassing the iterator invalidation mechanism introduced for StatementSync in recent releases.
A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation.
This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.
---------- Mensagem encaminhada --------- De: Rafael Gonzaga <work () rafaelgss dev> Data: quinta-feira, 18 de junho de 2026 às 10:33:52 UTC-3 Assunto: Re: Node.js security updates for all active release lines, June 2026 Para: nodejs-sec <nodejs-sec () googlegroups com>
The planned security releases are now available. You can read more about the details at https://nodejs.org/en/blog/vulnerability/june-2026-security-releases
Em quarta-feira, 10 de junho de 2026 às 11:53:26 UTC-3, Rafael Gonzaga escreveu:
The Node.js project will release new versions of all supported release lines on or shortly after June 17th, 2026
For more information, see: https://nodejs.org/en/blog/vulnerability/june-2026-security-releases <https://nodejs.org/en/blog/vulnerability/march-2026-security-releases>
A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a GOAWAY frame.
This vulnerability affects two supported release lines: Node.js 22 and Node.js 24.
A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat.
This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations.
This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.
---------- Mensagem encaminhada --------- De: Rafael Gonzaga <work () rafaelgss dev> Data: quarta-feira, 10 de junho de 2026 às 11:53:26 UTC-3 Assunto: Node.js security updates for all active release lines, June 2026 Para: nodejs-sec <nodejs-sec () googlegroups com>
The Node.js project will release new versions of all supported release lines on or shortly after June 17th, 2026
For more information, see: https://nodejs.org/en/blog/vulnerability/june-2026-security-releases <https://nodejs.org/en/blog/vulnerability/march-2026-security-releases>
Security researchers disclosed multiple critical vm2 sandbox escape vulnerabilities this week, including CVE-2026-26956 affecting Node.js 25. The flaws allow attackers running untrusted JavaScript inside vm2 to escape the sandbox and execute arbitrary code on the host system.
Info + analysis: https://thecybersecguru.com/news/vm2-sandbox-escape-vulnerability-cve-2026-26956/
End of life: 4/30/2029, End of support: 10/27/2027, Latest version: 26.13.0
A flaw in Node.js HMAC verification uses a non-constant-time comparison when validating user-provided signatures, potentially leaking timing information proportional to the number of matching bytes. Under certain threat models where high-resolution timing measurements are possible, this behavior could be exploited as a timing oracle to infer HMAC values.
Node.js already provides timing-safe comparison primitives used elsewhere in the codebase, indicating this is an oversight rather than an intentional design decision.
This vulnerability affects 20.x, 22.x, 24.x, and 25.x.
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.
A flaw in Node.js Permission Model filesystem enforcement leaves fs.realpathSync.native() without the required read permission checks, while all comparable filesystem functions correctly enforce them.
As a result, code running under --permission with restricted --allow-fs-read can still use fs.realpathSync.native() to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories.
This vulnerability affects 20.x, 22.x, 24.x, and 25.x processes using the Permission Model where --allow-fs-read is intentionally restricted.
A flaw in Node.js URL processing causes an assertion failure in native code when url.format() is called with a malformed internationalized domain name (IDN) containing invalid characters, crashing the Node.js process.
An incomplete fix for CVE-2024-36137 leaves FileHandle.chmod() and FileHandle.chown() in the promises API without the required permission checks, while their callback-based equivalents (fs.fchmod(), fs.fchown()) were correctly patched.
As a result, code running under --permission with restricted --allow-fs-write can still use promise-based FileHandle methods to modify file permissions and ownership on already-open file descriptors, bypassing the intended write restrictions.
This vulnerability affects 20.x, 22.x, 24.x, and 25.x processes using the Permission Model where --allow-fs-write is intentionally restricted.
A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOWUPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum value of 2³¹-1. The server correctly sends a GOAWAY frame, but the Http2Session object is never cleaned up.
A flaw in Node.js URL processing causes an assertion failure in native code when url.format() is called with a malformed internationalized domain name (IDN) containing invalid characters, crashing the Node.js process.
Updates are now available for the 25.x, 24.x, 22.x, and 20.x Node.js release lines to address:
3 high severity issues.
4 medium severity issues.
1 low severity issue.
This security release includes the following dependency updates to address public vulnerabilities:
c-ares (1.34.6) on 20.x, 22.x, 24.x, 25.x
undici (6.23.0, 7.18.0) on 20.x, 22.x, 24.x, 25.x
End of life: 6/1/2026, End of support: 4/1/2026, Latest version: 25.9.0
End of life: 4/30/2028, End of support: 10/20/2026, Latest version: 24.22.2
Rejected reason: This Record was REJECTED after determining it is not in compliance with CVE Program requirements regarding assignment for vulnerabilities
Rejected reason: This Record was REJECTED after determining it is not in compliance with CVE Program requirements regarding assignment for vulnerabilities