CISA list

Node.js versions

Node.js: update to 26.13.1, 24.22.3 or 22.23.5. 25, 23 and 21 and older have reached end of life in the lifecycle data.

Data: .

Which Node.js branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are counted at the end of the page.

Which Node.js branch to run
BranchStatusNewest safe releaseUpgrade to
2631 CVE recordsBug and security fixes until 27 October 202726.13.126.13.1 (this branch)
256 CVE recordsEnded on 1 June 2026None, the branch has ended26.13.1 (move to 26)
2437 CVE recordsSecurity fixes only until 30 April 202824.22.324.22.3 (this branch)
23Ended on 1 June 2025None, the branch has ended24.22.3 (move to 24)
2234 CVE recordsSecurity fixes only until 30 April 202722.23.522.23.5 (this branch)
21Ended on 1 June 2024None, the branch has ended22.23.5 (move to 22)
205 CVE recordsEnded on 30 April 2026None, the branch has ended22.23.5 (move to 22)
19Ended on 1 June 2023None, the branch has ended22.23.5 (move to 22)
18Ended on 30 April 2025None, the branch has ended22.23.5 (move to 22)
17Ended on 1 June 2022None, the branch has ended22.23.5 (move to 22)
16Ended on 11 September 2023None, the branch has ended22.23.5 (move to 22)
15Ended on 1 June 2021None, the branch has ended22.23.5 (move to 22)
14Ended on 30 April 2023None, the branch has ended22.23.5 (move to 22)
13Ended on 1 June 2020None, the branch has ended22.23.5 (move to 22)
12Ended on 30 April 2022None, the branch has ended22.23.5 (move to 22)
11Ended on 30 June 2019None, the branch has ended22.23.5 (move to 22)
10Ended on 30 April 2021None, the branch has ended22.23.5 (move to 22)
91 CVE recordEnded on 30 June 2018None, the branch has ended22.23.5 (move to 22)
81 CVE recordEnded on 31 December 2019None, the branch has ended22.23.5 (move to 22)
7Ended on 30 June 2017None, the branch has ended22.23.5 (move to 22)
61 CVE recordEnded on 30 April 2019None, the branch has ended22.23.5 (move to 22)
5Ended on 30 June 2016None, the branch has ended22.23.5 (move to 22)
42 CVE recordsEnded on 30 April 2018None, the branch has ended22.23.5 (move to 22)
3Ended, date not knownNone, the branch has ended22.23.5 (move to 22)
2Ended, date not knownNone, the branch has ended22.23.5 (move to 22)
1Ended, date not knownNone, the branch has ended22.23.5 (move to 22)

Exploited, or likely to be

CVE records for Node.js that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the releases that fix each where the record names them. 1 of the 7 records shown names one.

Exploited, or likely to be
RecordSigns of exploitationFixed in
CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX. This vulnerability affects Windows users of `path.join` API.7.5 High · published 18 July 2025Exploit-DB entryFixed in 24.4.1, 22.17.1, 20.19.4
CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2…8.2 High · published 9 April 2024EPSS 0.50 or moreThis page does not place it on a branch.
CVE-2022-32214The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).published 14 July 2022EPSS 0.50 or moreThis page does not place it on a branch.
CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 'unknownProtocol' are established. This leads to a leak of…published 3 March 2021EPSS 0.50 or moreThis page does not place it on a branch.
CVE-2022-32215The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle multi-line Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).published 14 July 2022EPSS 0.50 or moreThis page does not place it on a branch.
CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformedpublished 7 February 2020EPSS 0.50 or moreThis page does not place it on a branch.
CVE-2020-8277A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versions < 15.2.1, < 14.15.1, and < 12.19.1 by getting the…published 19 November 2020EPSS 0.50 or moreThis page does not place it on a branch.

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

The fixes are from 43 CVE records that the CVE Numbering Authorities HackerOne and the Node.js project published and that name Node.js. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

A branch that has ended is rarely named in a new record. That is not a sign that it is safe. Not tested by the project, treat as affected.

A release gets a page of its own when it fixes three or more CVE records, or any record that CISA lists as exploited or that EPSS rates 0.50 or more, and keeps it. Any other release is a row on its branch page.

104 records are not placed on a branch, so no branch or release row counts them: CVE-2017-15896, CVE-2017-15897, CVE-2018-7160, CVE-2018-7161, CVE-2018-7162, CVE-2018-7164, CVE-2018-7166, CVE-2018-7167, CVE-2018-12115 and CVE-2018-12116 and 94 others.

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)