<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 11 Nov 2026 23:51:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-123866 — Node.js is vulnerable to HTTP/2 response memory disclosure via a use-after-free during stream teardown</title>
      <link>https://db.gcve.eu/vuln/cve-2026-123866</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nodejs node&lt;/p&gt;
&lt;p&gt;A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections&amp;#39; response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RST_STREAM or by the server&amp;#39;s own per-stream timeout destroying the stream, the stream&amp;#39;s response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nodejs node&lt;/p&gt;
&lt;p&gt;A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections&amp;#39; response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RST_STREAM or by the server&amp;#39;s own per-stream timeout destroying the stream, the stream&amp;#39;s response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-123866</guid>
    </item>
  </channel>
</rss>
