VulnSea

nodejs has 45 CVEs on record between 2017 and 2026. Disclosure cadence is accelerating: 11 in the last 90 days against 1 in the 90 before. The busiest recent month was March 2026 with 11. The median CVSS is 7.5 (high), with 1 rated critical. None have a confirmed exploitation report. The dominant weakness classes are CWE-20 (8) and CWE-248 (7). Most affected products: node.js (31), undici (14).

CVEs per month

Last 12 months, by publish date

111201020304050607080910
Exploited share
0% vs 1% corpus
Median CVSS
7.5
Publish → KEV
—
Last 90 days
11 prev 1

Products

  • node.js 31
  • undici 14
45
Total CVEs
1
Critical
0
CISA KEV
0
Exploited

nodejs vulnerabilities

CVEs affecting nodejs, newest first. Open any entry for full detail, references, and exploit status.

45 CVEsRSS

CVE-2018-12122High· 7.5
7y ago

Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of Service: An attacker can cause a Denial of Service (DoS) by sending headers very slowly keeping HTTP or HTTPS connections and associated …

Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of Service: An attacker can cause a Denial of Service (DoS) by sending headers very slowly keeping HTTP or HTTPS connections and associated …

▾ Twilightnodejs · node.jsEPSS 41%via NVD
CVE-2018-12121High· 7.5
7y ago

Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Denial of Service with large HTTP headers: By using a combination of many requests with maximum sized headers (almost 80 KB per connection), and carefully timed c…

Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Denial of Service with large HTTP headers: By using a combination of many requests with maximum sized headers (almost 80 KB per connection), and carefully timed c…

▾ Twilightnodejs · node.jsEPSS 10%via NVD
CVE-2018-12120High· 8.1
7y ago

Node.js: All versions prior to Node.js 6.15.0: Debugger port 5858 listens on any interface by default: When the debugger is enabled with `node --debug` or `node debug`, it listens to port 5858 on all interfaces by default

Node.js: All versions prior to Node.js 6.15.0: Debugger port 5858 listens on any interface by default: When the debugger is enabled with `node --debug` or `node debug`, it listens to port 5858 on all interfaces by default. This may allow…

▾ Twilightnodejs · node.jsEPSS 4.3%via NVD
CVE-2018-12116High· 7.5
7y ago

Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provided Unicode data for the `path` option of an HTTP request, then data can be provided which will tr…

Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provided Unicode data for the `path` option of an HTTP request, then data can be provided which will tr…

▾ Twilightnodejs · node.jsEPSS 4.6%via NVD
CVE-2018-5407Medium· 4.7PoC
7y ago

Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.

Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.

▾ Twilightnodejs · node.jsEPSS 3.4%via NVD
CVE-2018-12115High· 7.5
8y ago

In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused to write outside of the…

In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused to write outside of the…

▾ Twilightnodejs · node.jsEPSS 7.8%via NVD
CVE-2018-7166High· 7.5⚖ disputed
8y ago

In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory

In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. This method is intended to be safe and only return initialized, or cleared, memory. The third argument …

▾ Twilightnodejs · node.jsEPSS 3.3%via NVD
CVE-2018-7167High· 7.5
8y ago

Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service

Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service. In order to address this vulnerability, the implementations of Buffer.alloc() and Buffer.fill() were updated so th…

▾ Twilightnodejs · node.jsEPSS 6.7%via NVD
CVE-2018-7164High· 7.5
8y ago

Node.js versions 9.7.0 and later and 10.x are vulnerable and the severity is MEDIUM

Node.js versions 9.7.0 and later and 10.x are vulnerable and the severity is MEDIUM. A bug introduced in 9.7.0 increases the memory consumed when reading from the network into JavaScript using the net.Socket object directly as a stream. …

▾ Twilightnodejs · node.jsEPSS 6.2%via NVD
CVE-2018-7162High· 7.5
8y ago

All versions of Node.js 9.x and 10.x are vulnerable and the severity is HIGH

All versions of Node.js 9.x and 10.x are vulnerable and the severity is HIGH. An attacker can cause a denial of service (DoS) by causing a node process which provides an http server supporting TLS server to crash. This can be accomplishe…

▾ Twilightnodejs · node.jsEPSS 6.6%via NVD
CVE-2018-7161High· 7.5
8y ago

All versions of Node.js 8.x, 9.x, and 10.x are vulnerable and the severity is HIGH

All versions of Node.js 8.x, 9.x, and 10.x are vulnerable and the severity is HIGH. An attacker can cause a denial of service (DoS) by causing a node server providing an http2 server to crash. This can be accomplished by interacting with…

▾ Twilightnodejs · node.jsEPSS 7.5%via NVD
CVE-2018-7160High· 8.8⚖ disputed
8y ago

The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution

The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or anoth…

▾ Twilightnodejs · node.jsEPSS 9.5%via NVD
CVE-2018-7159Medium· 5.3
8y ago

The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1 2` to be interpreted as having a value of `12`

The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1 2` to be interpreted as having a value of `12`. The HTTP specification does not allow for spaces …

▾ Sunlitnodejs · node.jsEPSS 3.5%via NVD
CVE-2018-7158High· 7.5
8y ago

The `'path'` module in the Node.js 4.x release line contains a potential regular expression denial of service (ReDoS) vector

The `'path'` module in the Node.js 4.x release line contains a potential regular expression denial of service (ReDoS) vector. The code in question was replaced in Node.js 6.x and later so this vulnerability only impacts all versions of N…

▾ Twilightnodejs · node.jsEPSS 3.4%via NVD
CVE-2017-14919High· 7.5
9y ago

Node.js before 4.8.5, 6.x before 6.11.5, and 8.x before 8.8.0 allows remote attackers to cause a denial of service (uncaught exception and crash) by leveraging a change in the zlib module 1.2.9 making 8 an invalid value for the windowBit…

Node.js before 4.8.5, 6.x before 6.11.5, and 8.x before 8.8.0 allows remote attackers to cause a denial of service (uncaught exception and crash) by leveraging a change in the zlib module 1.2.9 making 8 an invalid value for the windowBit…

▾ Twilightnodejs · node.jsEPSS 8.3%via NVD
nodejs vulnerabilities (CVEs) — page 2 · VulnSea