Skip to content

Commit 4d1ce7b

Browse files
mcollinaCopilot
andauthored
Final touches on EOL article (#7849)
* Final touches on EOL article Signed-off-by: Matteo Collina <[email protected]> * Update apps/site/pages/en/blog/announcements/node-18-eol-support.md Co-authored-by: Copilot <[email protected]> Signed-off-by: Matteo Collina <[email protected]> --------- Signed-off-by: Matteo Collina <[email protected]> Signed-off-by: Matteo Collina <[email protected]> Co-authored-by: Copilot <[email protected]>
1 parent 121f947 commit 4d1ce7b

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

apps/site/pages/en/blog/announcements/node-18-eol-support.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,13 +23,16 @@ Many ask, “**Why does the Node.js project not fix vulnerabilities for all rele
2323
If you are looking for additional proof points, here are a few examples of vulnerabilities that older versions of [Node.js](http://Node.js) are impacted:
2424

2525
- [https://nvd.nist.gov/vuln/detail/CVE-2025-23167](https://nvd.nist.gov/vuln/detail/CVE-2025-23167) affects 18, 16, 14 (llhttp) \- medium
26-
- [https://nvd.nist.gov/vuln/detail/CVE-2023-5678](https://nvd.nist.gov/vuln/detail/CVE-2023-5678) affects 16 e 14 (openssl) \- medium
27-
- [https://nvd.nist.gov/vuln/detail/CVE-2024-22019](https://nvd.nist.gov/vuln/detail/CVE-2024-22019) affects 16 e 14 (llhttp) \- high
26+
- [https://nvd.nist.gov/vuln/detail/CVE-2023-5678](https://nvd.nist.gov/vuln/detail/CVE-2023-5678) affects 16, 14 (openssl) \- medium
27+
- [https://nvd.nist.gov/vuln/detail/CVE-2024-22019](https://nvd.nist.gov/vuln/detail/CVE-2024-22019) affects 16, 14 (llhttp) \- high
2828
- [https://nvd.nist.gov/vuln/detail/CVE-2021-39135](https://nvd.nist.gov/vuln/detail/CVE-2021-39135) affects 14 (npm) \- high
2929

30-
This affects a staggering number of projects. Based on download statistics, Node.js v18 still accounts for approximately **50 million monthly downloads**, while legacy versions (v16 and below) continue to see **tens of millions of downloads per month**. That represents countless applications running on known vulnerable, unsupported runtime environments.
30+
This affects a staggering number of projects. Based on download statistics, Node.js v18, the most recent End-of-Life version, still accounts for approximately **50 million monthly downloads**, while earlier legacy versions (v16 and below) continue to see **tens of millions of downloads per month**. That represents countless applications running on known vulnerable, unsupported runtime environments.
3131

32-
\[suggested paragraph on [GitHub \- nodejs/is-my-node-vulnerable: package that checks if your Node.js installation is vulnerable to known security vulnerabilities](https://github.com/nodejs/is-my-node-vulnerable)\]
32+
You can check if your Node.js installation is vulnerable to known security
33+
vulnerabilities using the [is-my-node-vulnerable](https://github.com/nodejs/is-my-node-vulnerable)
34+
package. This tool checks your Node.js version against a database of known
35+
vulnerabilities and provides guidance on whether you need to upgrade.
3336

3437
## Node.js v22: The Smart Long-Term Choice
3538

0 commit comments

Comments
 (0)