nodejs nodejs Evented IO for v8 JavaScript

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in any nodejs product.

RSS Feeds for nodejs security vulnerabilities

Create a CVE RSS feed including security vulnerabilities found in nodejs products with stack.watch. Just hit watch, then grab your custom RSS feed url.

Products by nodejs Sorted by Most Security Vulnerabilities since 2018

nodejs node.js134 vulnerabilities

nodejs Undici12 vulnerabilities

nodejs1 vulnerability

Recent nodejs Security Advisories

Advisory Title Published
2025-05-08 Wednesday, May 14, 2025 Security Releases May 8, 2025
2025-03-31 Node.js Test CI Security Incident March 31, 2025
2025-03-07 Updates on CVE for End-of-Life Versions March 7, 2025
2025-01-14 Tuesday, January 21, 2025 Security Releases January 14, 2025
2025-01-06 Upcoming CVE for End-of-Life Node.js Versions January 6, 2025
2024-07-02 Tuesday, July 2, 2024 Security Releases July 2, 2024
2024-04-04 Tuesday, April 9, 2024 Security Releases April 4, 2024
2024-03-27 Wednesday, April 3, 2024 Security Releases March 27, 2024
2024-01-30 Tuesday February 6 2024 Security Releases January 30, 2024
2023-10-26 OpenSSL Recent Security Patches October 26, 2023

By the Year

In 2025 there have been 0 vulnerabilities in nodejs. Last year, in 2024 nodejs had 10 security vulnerabilities published. Right now, nodejs is on track to have less security vulnerabilities in 2025 than it did last year.




Year Vulnerabilities Average Score
2025 0 0.00
2024 10 6.90
2023 23 7.12
2022 28 7.25
2021 27 7.40
2020 15 7.96
2019 14 6.69
2018 20 6.95

It may take a day or so for new nodejs vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent nodejs Security Vulnerabilities

A command inject vulnerability allows an attacker to perform command injection on Windows applications

CVE-2024-3566 9.8 - Critical - April 10, 2024

A command inject vulnerability allows an attacker to perform command injection on Windows applications that indirectly depend on the CreateProcess function when the specific conditions are satisfied.

Command Injection

Undici is an HTTP/1.1 client, written from scratch for Node.js

CVE-2024-30260 4.3 - Medium - April 04, 2024

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici cleared Authorization and Proxy-Authorization headers for `fetch()`, but did not clear them for `undici.request()`. This vulnerability was patched in version(s) 5.28.4 and 6.11.1.

AuthZ

Undici is an HTTP/1.1 client, written from scratch for Node.js

CVE-2024-30261 3.5 - Low - April 04, 2024

Undici is an HTTP/1.1 client, written from scratch for Node.js. An attacker can alter the `integrity` option passed to `fetch()`, allowing `fetch()` to accept requests as valid even if they have been tampered. This vulnerability was patched in version(s) 5.28.4 and 6.11.1.

On Linux

CVE-2024-21892 7.8 - High - February 20, 2024

On Linux, Node.js ignores certain environment variables if those may have been set by an unprivileged user while the process is running with elevated privileges with the only exception of CAP_NET_BIND_SERVICE. Due to a bug in the implementation of this exception, Node.js incorrectly applies this exception even when certain other capabilities have been set. This allows unprivileged users to inject code that inherits the process's elevated privileges.

Code Injection

Node.js depends on multiple built-in utility functions to normalize paths provided to node:fs functions

CVE-2024-21891 8.8 - High - February 20, 2024

Node.js depends on multiple built-in utility functions to normalize paths provided to node:fs functions, which can be overwitten with user-defined implementations leading to filesystem permission model bypass through path traversal attack. This vulnerability affects all users using the experimental permission model in Node.js 20 and Node.js 21. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

Directory traversal

A vulnerability in Node.js HTTP servers

CVE-2024-22019 7.5 - High - February 20, 2024

A vulnerability in Node.js HTTP servers allows an attacker to send a specially crafted HTTP request with chunked encoding, leading to resource exhaustion and denial of service (DoS). The server reads an unbounded number of bytes from a single connection, exploiting the lack of limitations on chunk extension bytes. The issue can cause CPU and network bandwidth exhaustion, bypassing standard safeguards like timeouts and body size limits.

The permission model protects itself against path traversal attacks by calling path.resolve() on any paths given by the user

CVE-2024-21896 9.8 - Critical - February 20, 2024

The permission model protects itself against path traversal attacks by calling path.resolve() on any paths given by the user. If the path is to be treated as a Buffer, the implementation uses Buffer.from() to obtain a Buffer from the result of path.resolve(). By monkey-patching Buffer internals, namely, Buffer.prototype.utf8Write, the application can modify the result of path.resolve(), which leads to a path traversal vulnerability. This vulnerability affects all users using the experimental permission model in Node.js 20 and Node.js 21. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

The Node.js Permission Model does not clarify in the documentation that wildcards should be only used as the last character of a file path

CVE-2024-21890 6.5 - Medium - February 20, 2024

The Node.js Permission Model does not clarify in the documentation that wildcards should be only used as the last character of a file path. For example: ``` --allow-fs-read=/home/node/.ssh/*.pub ``` will ignore `pub` and give access to everything after `.ssh/`. This misleading documentation affects all users using the experimental permission model in Node.js 20 and Node.js 21. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

Undici is an HTTP/1.1 client, written from scratch for Node.js

CVE-2024-24758 4.5 - Medium - February 16, 2024

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Information Disclosure

Undici is an HTTP/1.1 client, written from scratch for Node.js

CVE-2024-24750 6.5 - Medium - February 16, 2024

Undici is an HTTP/1.1 client, written from scratch for Node.js. In affected versions calling `fetch(url)` and not consuming the incoming body ((or consuming it very slowing) will lead to a memory leak. This issue has been addressed in version 6.6.1. Users are advised to upgrade. Users unable to upgrade should make sure to always consume the incoming body.

Memory Leak

Built by Foundeo Inc., with data from the National Vulnerability Database (NVD). Privacy Policy. Use of this site is governed by the Legal Terms
Disclaimer
CONTENT ON THIS WEBSITE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. Always check with your vendor for the most up to date, and accurate information.