<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Node.js — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/nodejs" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by Node.js (nodejs).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/nodejs.png</url>
      <title>Node.js — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:08 GMT</lastBuildDate>
    <item>
      <title>CVE-2019-5739</title>
      <link>https://vulnogram.org/CVE-2019-5739</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2019-5739</guid>
      <description>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…</description>
      <pubDate>Thu, 28 Mar 2019 16:27:34 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2019-5737</title>
      <link>https://vulnogram.org/CVE-2019-5737</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2019-5737</guid>
      <description>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…</description>
      <pubDate>Thu, 28 Mar 2019 16:20:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-12123</title>
      <link>https://vulnogram.org/CVE-2018-12123</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-12123</guid>
      <description>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 m…</description>
      <pubDate>Wed, 28 Nov 2018 17:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-12122</title>
      <link>https://vulnogram.org/CVE-2018-12122</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-12122</guid>
      <description>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 ali…</description>
      <pubDate>Wed, 28 Nov 2018 17:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-12121</title>
      <link>https://vulnogram.org/CVE-2018-12121</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-12121</guid>
      <description>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…</description>
      <pubDate>Wed, 28 Nov 2018 17:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-12120</title>
      <link>https://vulnogram.org/CVE-2018-12120</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-12120</guid>
      <description>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 compu…</description>
      <pubDate>Wed, 28 Nov 2018 17:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-12116</title>
      <link>https://vulnogram.org/CVE-2018-12116</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-12116</guid>
      <description>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 secon…</description>
      <pubDate>Wed, 28 Nov 2018 17:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-7166</title>
      <link>https://vulnogram.org/CVE-2018-7166</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-7166</guid>
      <description>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 `e…</description>
      <pubDate>Tue, 21 Aug 2018 13:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-12115</title>
      <link>https://vulnogram.org/CVE-2018-12115</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-12115</guid>
      <description>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 `&apos;ucs2&apos;`, `&apos;ucs-2&apos;`, `&apos;utf16le&apos;` and `&apos;utf-16le&apos;`), `Buffer#write()` can be abused to write outside of the bounds of a…</description>
      <pubDate>Tue, 21 Aug 2018 13:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-7167</title>
      <link>https://vulnogram.org/CVE-2018-7167</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-7167</guid>
      <description>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…</description>
      <pubDate>Wed, 13 Jun 2018 16:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-7164</title>
      <link>https://vulnogram.org/CVE-2018-7164</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-7164</guid>
      <description>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 c…</description>
      <pubDate>Wed, 13 Jun 2018 16:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-7162</title>
      <link>https://vulnogram.org/CVE-2018-7162</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-7162</guid>
      <description>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…</description>
      <pubDate>Wed, 13 Jun 2018 16:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-7161</title>
      <link>https://vulnogram.org/CVE-2018-7161</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-7161</guid>
      <description>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 se…</description>
      <pubDate>Wed, 13 Jun 2018 16:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-7160</title>
      <link>https://vulnogram.org/CVE-2018-7160</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-7160</guid>
      <description>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 w…</description>
      <pubDate>Thu, 17 May 2018 14:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-7159</title>
      <link>https://vulnogram.org/CVE-2018-7159</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-7159</guid>
      <description>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 `Conte…</description>
      <pubDate>Thu, 17 May 2018 14:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2018-7158</title>
      <link>https://vulnogram.org/CVE-2018-7158</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2018-7158</guid>
      <description>The `&apos;path&apos;` 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. T…</description>
      <pubDate>Thu, 17 May 2018 14:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2017-15897</title>
      <link>https://vulnogram.org/CVE-2017-15897</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2017-15897</guid>
      <description>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, &apos;Buffer.alloc(0x100, &quot;This is not correctly encoded&quot;, &quot;hex&quot;);&apos; The buffer imp…</description>
      <pubDate>Mon, 11 Dec 2017 21:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2017-15896</title>
      <link>https://vulnogram.org/CVE-2017-15896</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2017-15896</guid>
      <description>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 wa…</description>
      <pubDate>Mon, 11 Dec 2017 21:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
