<?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://cve.radiocsirt.org</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>Mon, 16 Nov 2026 22:34:07 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-123865</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-123865</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: nodejs22, Alpaquita:25: nodejs24, Alpaquita:25: nodejs26, Alpaquita:stream: nodejs22, Alpaquita:stream: nodejs24, Alpaquita:stream: nodejs26, BellSoft Hardened Containers:25: nodejs22, BellSoft Hardened Containers:25: nodejs24, BellSoft Hardened Containers:25: nodejs26, BellSoft Hardened Containers:stream: nodejs22 and 2 more&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: nodejs22, Alpaquita:25: nodejs24, Alpaquita:25: nodejs26, Alpaquita:stream: nodejs22, Alpaquita:stream: nodejs24, Alpaquita:stream: nodejs26, BellSoft Hardened Containers:25: nodejs22, BellSoft Hardened Containers:25: nodejs24, BellSoft Hardened Containers:25: nodejs26, BellSoft Hardened Containers:stream: nodejs22 and 2 more&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-123865</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1531 — De multiples vulnérabilités ont été découvertes dans Node.js. Certaines d'entre elles permettent à un attaquant de prov…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1531</link>
      <description>certfr-2026-avi-1531</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1531</guid>
    </item>
    <item>
      <title>EUVD-2026-405154</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-405154</link>
      <description>EUVD-2026-405154</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-405154</guid>
    </item>
    <item>
      <title>fkie_cve-2026-123865</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-123865</link>
      <description>&lt;p&gt;An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js&amp;#39;s HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js&amp;#39;s HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-123865</guid>
    </item>
    <item>
      <title>GHSA-jj6m-hq7p-qvhr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jj6m-hq7p-qvhr</link>
      <description>&lt;p&gt;An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js&amp;#39;s HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js&amp;#39;s HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jj6m-hq7p-qvhr</guid>
    </item>
    <item>
      <title>NCSC-2026-0492 — Kwetsbaarheden verholpen in Node.js</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0492</link>
      <description>NCSC-2026-0492</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0492</guid>
    </item>
    <item>
      <title>RHSA-2026:99433 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:99433</link>
      <description>&lt;p&gt;nodejs: Node.js: Information disclosure via improper permission checks in recursive file watching nodejs: Node.js: Denial of service via abrupt disconnection during zlib compression nodejs: nodejs: Information disclosure via HTTPS parser re-entrancy nodejs: Node.js: Denial of service via HTTP/2 session resource leak during shutdown nodejs: Node.js: Information disclosure via use-after-free during HTTP/2 stream teardown nodejs: Node.js: Mutual TLS authorization bypass via incomplete SNI context configuration nodejs: Node.js: Information disclosure via invalid proxy configuration error messages nodejs: Node.js: Client certificate authentication bypass via TLS renegotiation nodejs: nodejs: Denial of Service via cancelled HTTP/2 file downloads nodejs: nodejs: Certificate validation bypass via TLS session cache reuse&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nodejs: Node.js: Information disclosure via improper permission checks in recursive file watching nodejs: Node.js: Denial of service via abrupt disconnection during zlib compression nodejs: nodejs: Information disclosure via HTTPS parser re-entrancy nodejs: Node.js: Denial of service via HTTP/2 session resource leak during shutdown nodejs: Node.js: Information disclosure via use-after-free during HTTP/2 stream teardown nodejs: Node.js: Mutual TLS authorization bypass via incomplete SNI context configuration nodejs: Node.js: Information disclosure via invalid proxy configuration error messages nodejs: Node.js: Client certificate authentication bypass via TLS renegotiation nodejs: nodejs: Denial of Service via cancelled HTTP/2 file downloads nodejs: nodejs: Certificate validation bypass via TLS session cache reuse&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:99433</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-123865</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123865</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: nodejs, Ubuntu:Pro:16.04:LTS: nodejs, Ubuntu:Pro:18.04:LTS: nodejs, Ubuntu:Pro:20.04:LTS: nodejs, Ubuntu:Pro:22.04:LTS: nodejs, Ubuntu:24.04:LTS: nodejs, Ubuntu:26.10: nodejs, Ubuntu:26.04:LTS: nodejs&lt;/p&gt;
&lt;p&gt;An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js&amp;#39;s HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. 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; Ubuntu:Pro:14.04:LTS: nodejs, Ubuntu:Pro:16.04:LTS: nodejs, Ubuntu:Pro:18.04:LTS: nodejs, Ubuntu:Pro:20.04:LTS: nodejs, Ubuntu:Pro:22.04:LTS: nodejs, Ubuntu:24.04:LTS: nodejs, Ubuntu:26.10: nodejs, Ubuntu:26.04:LTS: nodejs&lt;/p&gt;
&lt;p&gt;An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js&amp;#39;s HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123865</guid>
    </item>
  </channel>
</rss>
