Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,399
Published in 7 days
1,895
Critical in 30 days
489
Actively exploited
542
Clear filters

Results for “Node.js”

291 vulnerabilities
  1. High 8.1

    CVE-2020-8174 · Node.js

    napi_get_value_string_*() allows various kinds of memory corruption in node < 10.21.0, 12.18.0, and < 14.4.0.

    Published 24 Jul 2020 · Fixed in 10.21.0, 12.18.0, 14.4.0 · NVD
  2. High 7.4

    CVE-2020-8172 · Node.js

    TLS session reuse can lead to host certificate verification bypass in node version < 12.18.0 and < 14.4.0.

    Published 8 Jun 2020 · Fixed in 12.18.0, 14.4.0 · NVD
  3. High 7.5

    CVE-2020-11080 · Node.js, MySQL

    In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this…

    Published 3 Jun 2020 · Fixed in 10.21.0, 12.18.0 · NVD
  4. High 8.8

    CVE-2020-10531 · Google Chrome, Node.js

    An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. An integer overflow, leading to a heap-based buffer overflow, exists in the UnicodeString::doAppend() function in common/unistr.cpp.

    Published 12 Mar 2020 · Fixed in 10.21.0, 80.0.3987.122 · NVD
  5. High 8.1

    CVE-2014-9748 · Node.js

    The uv_rwlock_t fallback implementation for Windows XP and Server 2003 in libuv before 1.7.4 does not properly prevent threads from releasing the locks of other threads, which allows attackers to cause a denial of service (deadlock) or possibly have unspecified other impact by leveraging a race condition.

    Published 11 Feb 2020 · Fixed in 0.10.46, 0.12.15 · NVD
  6. Critical 9.8

    CVE-2019-15606 · Node.js

    Including trailing white space in HTTP header values in Nodejs 10, 12, and 13 causes bypass of authorization based on header value comparisons

    Published 7 Feb 2020 · Fixed in 10.19.0, 12.15.0, 13.8.0 · NVD
  7. Critical 9.8

    CVE-2019-15605 · Node.js

    HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed

    Published 7 Feb 2020 · Fixed in 10.19.0, 12.15.0, 13.8.0 · NVD
  8. High 7.5

    CVE-2019-15604 · Node.js

    Improper Certificate Validation in Node.js 10, 12, and 13 causes the process to abort when sending a crafted X.509 certificate

    Published 7 Feb 2020 · Fixed in 10.19.0, 12.15.0, 13.8.0 · NVD
  9. High 7.5

    CVE-2019-9518 · Apache Traffic Server, Node.js

    Some HTTP/2 implementations are vulnerable to a flood of empty frames, potentially leading to a denial of service. The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. The peer spends time processing each frame disproportionate to attack bandwidth. This can consume excess CPU.

    Published 13 Aug 2019 · Fixed in 8.16.1, 10.16.3, 12.8.1 · NVD
  10. High 7.5

    CVE-2019-9517 · Apache HTTP Server, Apache Traffic Server, Node.js

    Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service. The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually write (many of) the bytes on the wire. The attacker then sends a stream of requests for a large response object. Depending…

    Published 13 Aug 2019 · Fixed in 8.16.1, 10.16.3, 12.8.1 · NVD
  11. Medium 6.5

    CVE-2019-9516 · Apache Traffic Server, nginx, Node.js

    Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory.

    Published 13 Aug 2019 · Fixed in 8.16.1, 10.16.3, 12.8.1 · NVD
  12. High 7.5

    CVE-2019-9515 · Apache Traffic Server, F5 BIG-IP, Node.js

    Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess…

    Published 13 Aug 2019 · Fixed in 14.0.1.1, 14.1.2.1, 15.0.1.1 · NVD
  13. High 7.5

    CVE-2019-9514 · Apache Traffic Server, F5 BIG-IP, Node.js

    Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both.

    Published 13 Aug 2019 · Fixed in 14.0.1.1, 14.1.2.1, 15.0.1.1 · NVD
  14. High 7.5

    CVE-2019-9513 · Apache Traffic Server, nginx, Node.js

    Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.

    Published 13 Aug 2019 · Fixed in 8.16.1, 10.16.3, 12.8.1 · NVD
  15. High 7.5

    CVE-2019-9512 · Apache Traffic Server, Node.js

    Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

    Published 13 Aug 2019 · Fixed in 8.16.1, 10.16.3, 12.8.1 · NVD
  16. High 7.5

    CVE-2019-9511 · Apache Traffic Server, nginx, Node.js

    Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is…

    Published 13 Aug 2019 · Fixed in 8.16.1, 10.16.3, 12.8.1 · NVD
  17. High 7.5

    CVE-2019-5739 · Node.js

    Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier. Node.js 8.0.0 introduced a dedicated server.keepAliveTimeout which defaults to 5 seconds. The behavior in Node.js 6.16.0 and earlier is a potential Denial of Service (DoS) attack vector. Node.js 6.17.0 introduces server.keepAliveTimeout and the 5-second default.

    Published 28 Mar 2019 · NVD
  18. High 7.5

    CVE-2019-5737 · Node.js

    In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer…

    Published 28 Mar 2019 · Fixed in 8.15.1, 10.15.2, 11.10.1 · NVD
  19. Medium 5.9

    CVE-2019-1559 · F5 BIG-IP, Node.js, OpenSSL and 2 more

    If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is…

    Published 27 Feb 2019 · Fixed in 8.1.8, 8.15.1, 9.0.2 · NVD
  20. Medium 4.3

    CVE-2018-12123 · Node.js

    Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Hostname spoofing in URL parser for javascript protocol: If a Node.js application is using url.parse() to determine the URL hostname, that hostname can be spoofed by using a mixed case "javascript:" (e.g. "javAscript:") protocol (other protocols are not affected). If security decisions are made about the URL based on the…

    Published 28 Nov 2018 · Fixed in 8.14.0, 10.14.0, 11.3.0 · NVD
  21. High 7.5

    CVE-2018-12122 · Node.js

    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 resources alive for a long period of time.

    Published 28 Nov 2018 · Fixed in 8.14.0, 10.14.0, 11.3.0 · NVD
  22. High 7.5

    CVE-2018-12121 · Node.js

    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 completion of the headers, it is possible to cause the HTTP server to abort from heap allocation failure. Attack potential is mitigated by the use of a load…

    Published 28 Nov 2018 · Fixed in 8.14.0, 10.14.0, 11.3.0 · NVD
  23. High 8.1

    CVE-2018-12120 · Node.js

    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 remote computers to attach to the debug port and evaluate arbitrary JavaScript. The default interface is now localhost. It has always been possible to start the…

    Published 28 Nov 2018 · Fixed in 6.15.0 · NVD
  24. High 7.5

    CVE-2018-12116 · Node.js

    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 trigger a second, unexpected, and user-defined HTTP request to made to the same server.

    Published 28 Nov 2018 · Fixed in 6.15.0, 8.14.0 · NVD
  25. Medium 4.7

    CVE-2018-5407 · Node.js, OpenSSL

    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'.

    Published 15 Nov 2018 · Fixed in 6.14.4, 8.11.4, 10.9.0 · NVD
  26. Medium 5.9

    CVE-2018-0734 · Node.js, OpenSSL

    The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

    Published 30 Oct 2018 · Fixed in 6.15.0, 8.14.0, 11.3.0 · NVD
  27. Medium 5.9

    CVE-2018-0735 · Node.js, OpenSSL, MySQL

    The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

    Published 29 Oct 2018 · Fixed in 10.12.0, 11.3.0 · NVD
  28. High 7.5

    CVE-2018-7166 · Node.js

    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 specifying `encoding` can be passed as a number, this is misinterpreted by `Buffer's` internal "fill" method as the `start` to a fill operation. This flaw may be…

    Published 21 Aug 2018 · Fixed in 10.9.0 · NVD
  29. High 7.5

    CVE-2018-12115 · Node.js

    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 bounds of a single `Buffer`. Writes that start from the second-to-last position of a buffer cause a miscalculation of the maximum length of the input bytes to…

    Published 21 Aug 2018 · Fixed in 6.14.4, 8.11.4, 10.9.0 · NVD
  30. High 7.5

    CVE-2018-7167 · Node.js

    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 that they zero fill instead of hanging in these cases. All versions of Node.js 6.x (LTS "Boron"), 8.x (LTS "Carbon"), and 9.x are vulnerable. All versions of…

    Published 13 Jun 2018 · Fixed in 6.14.3, 8.11.3, 9.11.2 · NVD
  31. High 7.5

    CVE-2018-7164 · Node.js

    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. An attacker could use this cause a denial of service by sending tiny chunks of data in short succession. This vulnerability was restored by reverting to the…

    Published 13 Jun 2018 · Fixed in 9.11.2, 10.4.1 · NVD
  32. High 7.5

    CVE-2018-7162 · Node.js

    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 accomplished by sending duplicate/unexpected messages during the handshake. This vulnerability has been addressed by updating the TLS implementation.

    Published 13 Jun 2018 · Fixed in 9.11.2, 10.4.1 · NVD
  33. High 7.5

    CVE-2018-7161 · Node.js

    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 the http2 server in a manner that triggers a cleanup bug where objects are used in native code after they are no longer available. This has been addressed by…

    Published 13 Jun 2018 · Fixed in 8.11.3, 9.11.2, 10.4.1 · NVD
  34. High 7.5

    CVE-2018-0732 · Node.js, OpenSSL

    During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This could be exploited in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected…

    Published 12 Jun 2018 · Fixed in 8.8.1, 8.11.4, 10.9.0 · NVD
  35. Medium 6.5

    CVE-2017-16024 · Node.js

    The sync-exec module is used to simulate child_process.execSync in node versions <0.11.9. Sync-exec uses tmp directories as a buffer before returning values. Other users on the server have read access to the tmp directory, possibly allowing an attacker on the server to obtain confidential information from the buffer/tmp file, while it exists.

    Published 4 Jun 2018 · Fixed in 0.11.9 · NVD
  36. High 8.8

    CVE-2018-7160 · Node.js

    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 another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to…

    Published 17 May 2018 · Fixed in 6.14.0, 8.11.0, 9.10.0 · NVD
  37. Medium 5.3

    CVE-2018-7159 · Node.js

    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 in the `Content-Length` value and the Node.js HTTP parser has been brought into line on this particular difference. The security risk of this flaw to Node.js…

    Published 17 May 2018 · Fixed in 6.14.0, 8.11.0, 9.10.0 · NVD
  38. High 7.5

    CVE-2018-7158 · Node.js

    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 Node.js 4.x. The regular expression, `splitPathRe`, used within the `'path'` module for the various path parsing functions, including `path.dirname()`,…

    Published 17 May 2018 · NVD
  39. High 7.5

    CVE-2018-1000168 · Node.js

    nghttp2 version >= 1.10.0 and nghttp2 <= v1.31.0 contains an Improper Input Validation CWE-20 vulnerability in ALTSVC frame handling that can result in segmentation fault leading to denial of service. This attack appears to be exploitable via network client. This vulnerability appears to have been fixed in >= 1.31.1.

    Published 8 May 2018 · Fixed in 10.4.1 · NVD
  40. Low 3.1

    CVE-2017-15897 · Node.js

    Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, 'Buffer.alloc(0x100, "This is not correctly encoded", "hex");' The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases.

    Published 11 Dec 2017 · Fixed in 8.9.3, 9.2.1 · NVD
  41. Critical 9.1

    CVE-2017-15896 · Node.js

    Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS handshake failure. The result was that an active network attacker could send application data to Node.js using the TLS or HTTP2 modules in a way that bypassed TLS authentication and encryption.

    Published 11 Dec 2017 · Fixed in 6.12.2, 8.9.3, 9.2.1 · NVD
  42. Medium 5.9

    CVE-2017-3738 · Node.js, OpenSSL

    There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH1024 are considered just feasible, because most of the work necessary to deduce…

    Published 7 Dec 2017 · Fixed in 6.12.2, 8.9.3, 9.2.1 · NVD
  43. High 7.5

    CVE-2017-14919 · Node.js

    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 windowBits parameter.

    Published 30 Oct 2017 · NVD
  44. High 7.5

    CVE-2014-3744 · Node.js

    Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary files via a %2e%2e (encoded dot dot) in an unspecified path.

    Published 23 Oct 2017 · NVD
  45. High 7.5

    CVE-2015-7384 · Node.js

    Node.js 4.0.0, 4.1.0, and 4.1.1 allows remote attackers to cause a denial of service.

    Published 10 Oct 2017 · NVD
  46. High 7.5

    CVE-2017-14849 · Node.js

    Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the pathname validation used by unspecified community modules.

    Published 28 Sept 2017 · NVD
  47. Medium 6.5

    CVE-2015-2927 · Node.js

    node 0.3.2 and URONode before 1.0.5r3 allows remote attackers to cause a denial of service (bandwidth consumption).

    Published 20 Sept 2017 · NVD
  48. High 7.5

    CVE-2017-11499 · Node.js

    Node.js v4.0 through v4.8.3, all versions of v5.x, v6.0 through v6.11.0, v7.0 through v7.10.0, and v8.0 through v8.1.3 was susceptible to hash flooding remote DoS attacks as the HashTable seed was constant across a given released version of Node.js. This was a result of building with V8 snapshots enabled by default which caused the initially randomized seed to be overwritten on startup.

    Published 25 Jul 2017 · NVD
  49. High 7.5

    CVE-2017-1000381 · c-ares, Node.js

    The c-ares function `ares_parse_naptr_reply()`, which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer if the passed in DNS response packet was crafted in a particular way.

    Published 7 Jul 2017 · Fixed in 6.11.1, 7.10.1, 8.1.4 · NVD
  50. Critical 9.8

    CVE-2016-9843 · MariaDB, Node.js, Java and 1 more

    The crc32_big function in crc32.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact via vectors involving big-endian CRC calculation.

    Published 23 May 2017 · Fixed in 10.1.37, 10.2.19, 10.3.11 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.