<?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 20:18:13 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-106070</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-106070</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: nodejs26, Alpaquita:stream: nodejs26, BellSoft Hardened Containers:25: nodejs26, BellSoft Hardened Containers:stream: nodejs26&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: nodejs26, Alpaquita:stream: nodejs26, BellSoft Hardened Containers:25: nodejs26, BellSoft Hardened Containers:stream: nodejs26&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-106070</guid>
    </item>
    <item>
      <title>BIT-node-2026-106070</title>
      <link>https://cve.radiocsirt.org/vuln/bit-node-2026-106070</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: node&lt;/p&gt;
&lt;p&gt;A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails.&lt;/p&gt;
&lt;p&gt;When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x**.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: node&lt;/p&gt;
&lt;p&gt;A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails.&lt;/p&gt;
&lt;p&gt;When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x**.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-node-2026-106070</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-RS73097 — flaw in the Node</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-rs73097</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: nodejs&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the nodejs package. A flaw in the Node.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: nodejs&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the nodejs package. A flaw in the Node.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-rs73097</guid>
    </item>
    <item>
      <title>EUVD-2026-391673</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391673</link>
      <description>EUVD-2026-391673</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391673</guid>
    </item>
    <item>
      <title>fkie_cve-2026-106070</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-106070</link>
      <description>&lt;p&gt;A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails.&lt;/p&gt;
&lt;p&gt;When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x**.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails.&lt;/p&gt;
&lt;p&gt;When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x**.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-106070</guid>
    </item>
    <item>
      <title>GHSA-c2qw-fgxm-vxx4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c2qw-fgxm-vxx4</link>
      <description>&lt;p&gt;A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails.&lt;/p&gt;
&lt;p&gt;When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x**.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails.&lt;/p&gt;
&lt;p&gt;When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x**.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c2qw-fgxm-vxx4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-106070</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-106070</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;A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive. This vulnerability affects Node.js **26.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;A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive. This vulnerability affects Node.js **26.x**.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-106070</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4117 — Node.js: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4117</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen und um beliebigen Programmcode auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen und um beliebigen Programmcode auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4117</guid>
    </item>
  </channel>
</rss>
