<?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 21:29:49 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-123862</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-123862</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-123862</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-405148</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-405148</link>
      <description>EUVD-2026-405148</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-405148</guid>
    </item>
    <item>
      <title>fkie_cve-2026-123862</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-123862</link>
      <description>&lt;p&gt;An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write&amp;#39;s callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream&amp;#39;s error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write&amp;#39;s callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream&amp;#39;s error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. 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-123862</guid>
    </item>
    <item>
      <title>GHSA-827v-4jh3-rppr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-827v-4jh3-rppr</link>
      <description>&lt;p&gt;An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write&amp;#39;s callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream&amp;#39;s error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. This vulnerability affects Node.js 26.x, 24.x, and 22.x.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write&amp;#39;s callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream&amp;#39;s error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. 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-827v-4jh3-rppr</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-123862</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123862</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 uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write&amp;#39;s callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream&amp;#39;s error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. 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 uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write&amp;#39;s callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream&amp;#39;s error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. 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-123862</guid>
    </item>
  </channel>
</rss>
