CISA list

● Branch of Node.js

Node.js 25

Node.js 25 reached end of life on 1 June 2026 and gets no fixes. Move to 26.13.1 or newer.

Data: .

Records with no fixed release for 25

These records name the branch as affected and name no release that ends the range.

Records with no fixed release for 25
RecordSigns of exploitationFixed in
CVE-2025-55130A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a…7.1 High · published 20 January 2026NoneThe record names no fixed release for 25, 24, 22 and 20.
CVE-2026-21636A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when `--permission` is enabled. Even without `--allow-net`, attacker-controlled inputs…5.8 Medium · published 20 January 2026NoneThe record names no fixed release for 25.
CVE-2026-21716An 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…3.3 Low · published 30 March 2026NoneThe record names no fixed release for 25, 24, 22 and 20.
CVE-2026-21714A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum value of 231-1. The…5.3 Medium · published 30 March 2026NoneThe record names no fixed release for 25, 24, 22 and 20.
CVE-2026-21712A 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…5.7 Medium · published 30 March 2026NoneThe record names no fixed release for 25 and 24.
CVE-2025-55132A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via `futimes()` even when the process has only read permissions. Unlike `utimes()`, `futimes()`…2.8 Low · published 20 January 2026NoneThe record names no fixed release for 25, 24, 22 and 20.

Node.js 25 in dates

WhatWhen
Released15 October 2025
Bug and security fixes end1 April 2026
Security fixes end1 June 2026
Newest release25.9.0 (1 April 2026)

What this page says

Since 1 June 2026, the CVE Numbering Authorities HackerOne and the Node.js project have published 33 CVE records that name Node.js. None of them names Node.js 25.

A record names the branches the project tested, and a branch that has ended is rarely among them. That does not make Node.js 25 safe. Not tested by the project, treat as affected.

A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)