OSSeva Blog
SecurityNode.js Vulnerabilities by Version: CVEs for Node 18, 20, 22, 24 and 26 After the 11 November 2026 Release
Node.js security releases and which versions are patched
Node.js has shipped nine security releases since January 2025. The latest, on 11 November 2026, fixed 16 issues, 7 of them rated high, in 22.23.5, 24.22.3 and 26.13.1. Node.js 20, which ended on 30 April 2026, received no fix from the June, July, October or November 2026 releases. Node.js 18, which ended on 30 April 2025, has had none since January 2025.
On 18 or 20? Node.js end-of-life dates counts the security releases each ended line has missed, and Node.js extended support covers how patched runtimes close them. Node.js CVEs since end of life this month lists the 11 November 2026 release.
Running Node.js in production? OSSeva patches and supports it, end-of-life versions included.
Node.js extended support: what is coveredTally by line: releases missed and High CVEs since end of life
Node.js 18 has missed 8 security releases and 24 High-rated CVEs since it ended, and Node.js 20 has missed 4 releases and 16, while Node.js 22, 24 and 26 have missed none. The counts come from the release table below and include every issue the Node.js announcements rate High; Medium and Low issues are extra.
| Line | End of life | Security releases that patched it (since Jan 2025) | Releases missed since end of life | High-rated CVEs missed |
|---|---|---|---|---|
| Node.js 18 | 30 April 2025 | 1 | 8 | 24 |
| Node.js 20 | 30 April 2026 | 5 | 4 | 16 |
| Node.js 22 | 30 April 2027 | 9 | 0 | 0 |
| Node.js 24 | 30 April 2028 | 8 | 0 | 0 |
| Node.js 26 | 30 April 2029 | 4 | 0 | 0 |
Last tallied on 17 November 2026, after the 11 November release. The next row to change is Node.js 22 on 30 April 2027. How fast a fix reaches an ended line depends on its source: OSSeva's Node.js extended support fixes Critical CVEs within 48 hours and High within 7 days, and every other provider publishes its own windows.
Which Node.js lines get security fixes
Three Node.js release lines get security fixes today: 22, 24 and 26. Node.js 22 is in Maintenance LTS until 30 April 2027. Node.js 24 moved from Active LTS to Maintenance LTS on 20 October 2026 and is supported until 30 April 2028. Node.js 26 has been an LTS line since 28 October 2026 and is supported until 30 April 2029. Node.js 20 reached end of life on 30 April 2026 and Node.js 18 on 30 April 2025. Every Node.js security release since those dates has patched the supported lines only. The last security release for Node.js 20 was 20.20.2 in March 2026, and for Node.js 18 it was 18.20.6 in January 2025.
How Node.js treats end-of-life lines
The Node.js project does not assess security reports against end-of-life lines, and each security release announcement says that end-of-life versions "are always affected". In January 2025 the project issued three CVEs that simply marked end-of-life versions as vulnerable (CVE-2025-23087, CVE-2025-23088 and CVE-2025-23089). The CVE Program rejected them. The project then said that new CVEs would include end-of-life releases in their applicability unless it had information showing a CVE does not apply.
You can see the effect in NVD. The version range for CVE-2026-21637 starts at 4.0.0, and the range for CVE-2026-21710 covers every release up to 20.20.1, so a scanner will flag Node.js 18 and 16 for both alongside unpatched 20.x.
Security releases since January 2025
| Release | Lines patched | CVEs rated High by Node.js | Fixed versions |
|---|---|---|---|
| January 2025 | 18, 20, 22, 23 | CVE-2025-23083 | 18.20.6, 20.18.2, 22.13.1, 23.6.1 |
| May 2025 | 20, 22, 23, 24 | CVE-2025-23166 | 20.19.2, 22.15.1, 23.11.1, 24.0.2 |
| July 2025 | 20, 22, 24 | CVE-2025-27209, CVE-2025-27210 | 20.19.4, 22.17.1, 24.4.1 |
| January 2026 | 20, 22, 24, 25 | CVE-2025-55130, CVE-2025-55131, CVE-2025-59465 | 20.20.0, 22.22.0, 24.13.0, 25.3.0 |
| March 2026 | 20, 22, 24, 25 | CVE-2026-21637, CVE-2026-21710 | 20.20.2, 22.22.2, 24.14.1, 25.8.2 |
| June 2026 | 22, 24, 26 | CVE-2026-48933, CVE-2026-48618 | 22.23.0, 24.17.0, 26.3.1 |
| July 2026 | 22, 24, 26 | CVE-2026-56846, CVE-2026-56848, CVE-2026-58043 | 22.23.2, 24.18.1, 26.5.1 |
| 21 October 2026 | 22, 24, 26 | CVE-2026-111497, CVE-2026-105482, CVE-2026-105483, CVE-2026-106069 | 22.23.4, 24.22.1, 26.12.1 |
| 11 November 2026 | 22, 24, 26 | CVE-2026-123863, CVE-2026-123864, CVE-2026-123865, CVE-2026-123866, CVE-2026-126051, CVE-2026-123872, CVE-2026-123874 | 22.23.5, 24.22.3, 26.13.1 |
Node.js 18 drops out after January 2025 and Node.js 20 after March 2026. Each release also fixed Medium and Low issues not listed here; the announcements on nodejs.org have the full lists. The October 2026 row is from the Node.js October 2026 security releases announcement, which lists 4 High, 3 Medium and 3 Low issues. Its four High issues are the Brotli decoder flaw that can lead to remote code execution, two TLS certificate hostname bypasses and a dns.resolve flaw; each now has a page in the CVE directory. The November 2026 row is from the Node.js November 2026 security releases announcement, which lists 7 High, 6 Medium and 3 Low issues; one of the High issues, CVE-2026-123863, affects 24 and 26 only.
Notable Node.js CVEs by release line
CVSS is NVD's own score where NVD has analysed the record and the score filed by the CNA, HackerOne or OpenJS, where it has not. Many Node.js records sit in NVD's Deferred status, so the two sources are mixed.
| CVE | Issue | CVSS | Fixed in | End-of-life lines |
|---|---|---|---|---|
| CVE-2025-55130 | Permission model bypass with crafted relative symlinks gives file read and write outside the allowlist | 9.1 (NVD) | 20.20.0, 22.22.0, 24.13.0, 25.3.0 | 18 not patched |
| CVE-2026-58043 | Permission model path matching over-grants file system access across prefix boundaries | 8.4 (NVD) | 22.23.2, 24.18.1, 26.5.1 | 20 and 18 not patched |
| CVE-2025-23083 | Permission model: diagnostics_channel exposes internal worker constructors | 7.7 | 20.18.2, 22.13.1, 23.6.1 | Not listed for 18 |
| CVE-2025-23166 | An error in a background cryptographic operation crashes the process | 7.5 | 20.19.2, 22.15.1, 23.11.1, 24.0.2 | 18 not patched |
| CVE-2025-27210 | Windows device names such as CON, PRN and AUX bypass path traversal protection (incomplete fix for CVE-2025-23084) | 7.5 | 20.19.4, 22.17.1, 24.4.1 | 18 not patched |
| CVE-2025-27209 | HashDoS reintroduced by the V8 string hashing change in Node.js 24 | 7.5 | 24.4.1 | 24 only |
| CVE-2025-59465 | A malformed HTTP/2 HEADERS frame crashes the process | 7.5 | 20.20.0, 22.22.0, 24.13.0, 25.3.0 | 18 not patched |
| CVE-2025-59466 | Stack overflow errors become uncatchable when async_hooks is enabled | 7.5 (NVD) | 20.20.0, 22.22.0, 24.13.0, 25.3.0 | 18 not patched |
| CVE-2025-55131 | Buffer.alloc and Uint8Array can return memory that is not zero-filled when a vm timeout interrupts allocation | 7.1 | 20.20.0, 22.22.0, 24.13.0, 25.3.0 | 18 not patched |
| CVE-2026-21637 | Exceptions in TLS PSK, ALPN and SNI callbacks crash the server or leak file descriptors | 7.5 (NVD) | 20.20.0, 22.22.0, 24.13.0, 25.3.0; completed in 20.20.2, 22.22.2, 24.14.1, 25.8.2 | NVD range starts at 4.0.0 |
| CVE-2026-21710 | A header named __proto__ crashes servers that read req.headersDistinct | 7.5 | 20.20.2, 22.22.2, 24.14.1, 25.8.2 | NVD range covers every release to 20.20.1 |
| CVE-2026-48933 | WebCrypto AES input that is a multiple of 2 GiB crashes the process | 7.5 | 22.23.0, 24.17.0, 26.3.1 | 20 and 18 not patched |
| CVE-2026-48618 | Unicode dot separators can bypass the TLS wildcard depth check, because the resolver and the verifier normalise hostnames differently | 6.5 (NVD) | 22.23.0, 24.17.0, 26.3.1 | 20 and 18 not patched |
| CVE-2026-56846 | Retained HTTP/2 header blocks evade maxSessionMemory, allowing remote memory exhaustion | 7.5 | 22.23.2, 24.18.1 | 20 and 18 not patched |
| CVE-2026-56848 | Re-entrant HTTP/2 send causes a heap use-after-free | 7.5 | 22.23.2, 24.18.1, 26.5.1 | 20 and 18 not patched |
| CVE-2026-111497 | Brotli decoder out-of-bounds write in node:zlib can lead to remote code execution | 9.8 (NVD) | 22.23.4, 24.22.1, 26.12.1 | 20 and 18 not patched |
| CVE-2026-105482 | dns.resolve*() and dns.reverse() truncate a hostname at a NUL character (incomplete fix for CVE-2026-48930) | 7.4 | 22.23.4, 24.22.1, 26.12.1 | 20 and 18 not patched |
| CVE-2026-105483 | tls.checkServerIdentity() accepts a certificate for an IPv4 host written in fullwidth digits (24 and 26 only) | 7.4 | 24.22.1, 26.12.1 | 20 and 18 not patched |
| CVE-2026-106069 | TLS certificate validated against a different IP than the one connected to, for leading-zero IPv4 literals | 7.4 | 22.23.4, 24.22.1, 26.12.1 | 20 and 18 not patched |
| CVE-2026-123863 | An unauthenticated HTTP/2 client aborts the server through an assertion in session teardown (24 and 26 only) | 8.2 | 24.22.3, 26.13.1 | 20 and 18 not patched |
| CVE-2026-123864 | A zero-length TLS write re-enters the HTTP parser and copies heap memory into the request body | 8.1 | 22.23.5, 24.22.3, 26.13.1 | 20 and 18 not patched |
| CVE-2026-123865 | HTTP/2 sessions leak memory and file descriptors after a protocol error during shutdown (incomplete fix for CVE-2026-48937) | 7.5 | 22.23.5, 24.22.3, 26.13.1 | 20 and 18 not patched |
| CVE-2026-123866 | HTTP/2 stream teardown can send freed response memory to the peer | 7.5 | 22.23.5, 24.22.3, 26.13.1 | 20 and 18 not patched |
| CVE-2026-126051 | A deferred TLS handshake callback raises an uncaught exception and ends the server process (24 and 26 only) | 7.5 | 24.22.3, 26.13.1 | 20 and 18 not patched |
| CVE-2026-123872 | TLS 1.2 renegotiation lets a client change the servername to bypass per-host client-certificate policy | 8.1 | 22.23.5, 24.22.3, 26.13.1 | 20 and 18 not patched |
| CVE-2026-123874 | HTTP/2 use-after-free when a respondWithFile() stream is reset during a pending write (24 and 26 only) | 7.5 | 24.22.3, 26.13.1 | 20 and 18 not patched |
"Not patched" means the line was out of support when the fix shipped and the project did not assess it. Under the project's policy, treat it as affected.
Node.js 26
Node.js 26 was released in May 2026 and has had four security releases, in June, July, October and November 2026. It became LTS on 28 October 2026 and is supported until 30 April 2029. The latest release at the time of writing is 26.13.1. Node.js 27 is scheduled for April 2027, with end of life on 30 April 2030.
Node.js 24
Node.js 24 has been patched in every security release since May 2025 and is supported until 30 April 2028. It moved from Active LTS to Maintenance on 20 October 2026. One CVE affects 24 alone: CVE-2025-27209, a HashDoS that came back with the V8 version Node.js 24 shipped, fixed in 24.4.1.
Node.js 22
Node.js 22 has been in Maintenance LTS since October 2025 and reaches end of life on 30 April 2027, about five months away. It has been patched in every security release in the table above, and its current release is 22.23.5. It is the next line to drop out of security releases, so estates on 22 should plan the move to 24 or 26 now.
Node.js 20
Node.js 20 reached end of life on 30 April 2026. Its last release, 20.20.2 in March 2026, fixed CVE-2026-21637 and CVE-2026-21710. The June and July 2026 security releases then fixed five CVEs that Node.js rated High (CVE-2026-48933, CVE-2026-48618, CVE-2026-56846, CVE-2026-56848 and CVE-2026-58043) on 22, 24 and 26 only. The October 2026 release fixed four more that Node.js rated High, and the November 2026 release seven more, again on 22, 24 and 26 only. The project did not assess 20 for any of them. See Node.js 20 end of life.
Node.js 18
Node.js 18 reached end of life on 30 April 2025. Its last security release was 18.20.6 in January 2025, and its final release was 18.20.8 in March 2025. Eight security releases have shipped since without an 18.x build, and between them they fixed 24 issues that Node.js rated High. Some apply only to features or V8 versions in newer lines, such as the permission model CVEs and CVE-2025-27209, but HTTP/2, TLS and HTTP header crashes such as CVE-2025-59465 and CVE-2026-21710 sit in code that Node.js 18 also has. See Node.js 18 end of life.
Node.js 16 and older
Node.js 16 reached end of life on 11 September 2023, and its final release was 16.20.2 in August 2023. It has missed every security release since, including all of the ones above. See Node.js 16 end of life.
Node.js remote code execution CVEs
Code execution bugs are rare in Node.js core. Most core CVEs are denial of service, request smuggling, TLS verification mistakes or permission model bypasses. The ones closest to code execution are these:
- CVE-2024-27980 (8.1). On Windows, child_process.spawn and spawnSync handled batch files in a way that let a malicious argument inject commands even with the shell option disabled. Fixed in April 2024 in 18.20.2, 20.12.2 and 21.7.3.
- CVE-2024-36138 (8.1). A bypass of that fix using other batch file extensions, fixed in July 2024 in 18.20.4, 20.15.1 and 22.4.1. Node.js 16 has neither fix.
- CVE-2026-56848 (7.5). A heap use-after-free in HTTP/2 handling, which is a memory safety bug in code that parses network input. Fixed in 22.23.2, 24.18.1 and 26.5.1, with no fix for 20 or 18.
- CVE-2025-55130 (9.1) and CVE-2026-58043 (8.4). These matter if you rely on the --permission flag to contain untrusted code, because both let that code read or write files outside its allowlist.
Many code execution findings in Node.js applications come from npm dependencies rather than the runtime. Those are fixed by upgrading the dependency, and a runtime upgrade does not touch them.
Who provides CVE patches for Node.js 18 and 20 now?
The Node.js project does not. Its end-of-life page says commercial security fixes for versions past maintenance come through the OpenJS Foundation Ecosystem Sustainability Program from HeroDevs, NodeSource and TuxCare. Of those, HeroDevs and TuxCare publish patched Node.js 18 and 20 runtimes, and two more providers cover the lines in narrower ways. The table repeats the facts from our Node.js end-of-life support providers comparison, where each is sourced.
| Provider | Node.js lines covered | How fixes arrive |
|---|---|---|
| HeroDevs Never-Ending Support | 12, 14, 16, 18 and 20 | Drop-in container images and binaries, with SLA-backed patch delivery tied to severity (SLA on request) |
| TuxCare Endless Lifecycle Support | 12, 14, 16, 18 and 20; 22 to be added when it reaches end of life | Signed patches from TuxCare-hosted repositories, with SBOM and VEX documents |
| OSSeva | 14, 16, 18 and 20 now; 22 after 30 April 2027 | GPG-signed Docker images, apt and yum packages and binaries |
| Canonical (Ubuntu Pro) | The version each Ubuntu release ships, such as 18.19.1 on Ubuntu 24.04 | Through apt, with ESM Apps |
OSSeva publishes this list and is one of the providers in it. HeroDevs and TuxCare were last read on their own pages on 17 November 2026 and Canonical on 28 October 2026; the Node.js project's end-of-life page was read on 18 November 2026. Nothing here covers Node.js 22, 24 or 26, which the project still patches.
What to do on each line
- 26 and 24. Stay on the latest patch release. Security releases have come every few months, with no fixed calendar.
- 22. Stay current, and schedule the move before 30 April 2027.
- 20 and 18. Upgrade to 22 or later, or take patched builds from a supplier that backports fixes. Pinning to 20.20.2 or 18.20.8 leaves every CVE fixed since then open.
Where OSSeva fits
OSSeva backports Node.js security fixes, including V8 and libuv CVEs, to end-of-life lines from 14.x to 20.x, and ships them as signed builds through Docker images, apt, yum or plain binaries. They are available now on the Patch, Assure and Operate tiers. Assure adds transitive npm dependency scanning and a SOC 2 and PCI DSS attestation package, and Operate adds 24/7 runtime monitoring with named Node.js engineers. See Node.js support and the Node.js end of life tracker.
Tags
Related articles
Running Node.js After End of Life: Enterprise Guide for Node 18, 20 and 22
March 12, 2026SecurityMySQL vulnerabilities by version: Oracle's 2026 advisories for 8.0, 8.4 and 9.7
November 17, 2026SecurityNovember 2026 Patch Tuesday: the last .NET 8 and .NET 9 updates
November 11, 2026SecurityApache Storm Vulnerabilities by Version: CVEs for Storm 1.2, 2.x and 3.x
October 6, 2026Securityetcd Vulnerabilities by Version: CVEs for etcd 3.3, 3.4, 3.5, 3.6 and 3.7
October 6, 2026SecurityClickHouse Vulnerabilities by Version: CVEs for ClickHouse 22.x to 26.x, LTS and Stable
October 6, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?