<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T22:09:31.240434+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/alsa-2023:5849</id>
    <title>ALSA-2023:5849 — Important: nodejs:18 security update</title>
    <updated>2026-10-02T22:09:31.648432+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:9: nodejs, AlmaLinux:9: nodejs-devel, AlmaLinux:9: nodejs-docs, AlmaLinux:9: nodejs-full-i18n, AlmaLinux:9: nodejs-nodemon, AlmaLinux:9: nodejs-packaging, AlmaLinux:9: nodejs-packaging-bundler, AlmaLinux:9: npm</p>
<p>Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.</p>
<p>Security Fix(es):</p>
<p>* HTTP/2: Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack) (CVE-2023-44487)
* nodejs: integrity checks according to policies can be circumvented (CVE-2023-38552)
* nodejs: code injection via WebAssembly export names (CVE-2023-39333)
* node-undici: cookie leakage (CVE-2023-45143)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/alsa-2023:5849"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2023-07176</id>
    <title>bdu:2023-07176</title>
    <updated>2026-10-02T22:09:31.648516+00:00</updated>
    <content>bdu:2023-07176</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2023-07176"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2023-38552</id>
    <title>BELL-CVE-2023-38552</title>
    <updated>2026-10-02T22:09:31.648534+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: nodejs, Alpaquita:stream: nodejs, BellSoft Hardened Containers:23: nodejs, BellSoft Hardened Containers:stream: nodejs</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2023-38552"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-node-2023-38552</id>
    <title>BIT-node-2023-38552</title>
    <updated>2026-10-02T22:09:31.648557+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: node</p>
<p>When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to the node's policy implementation, thus effectively disabling the integrity check.
Impacts:
This vulnerability affects all users using the experimental policy mechanism in all active release lines: 18.x and, 20.x.
Please note that at the time this CVE was issued, the policy mechanism is an experimental feature of Node.js.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-node-2023-38552"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0145</id>
    <title>certfr-2024-avi-0145 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;les produits IBM&lt;/span&gt;. Certaines d'entre el…</title>
    <updated>2026-10-02T22:09:31.648579+00:00</updated>
    <content>certfr-2024-avi-0145</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2024-avi-0145"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-fi53720</id>
    <title>Withdrawn: CLEANSTART-2026-FI53720 — Security fixes in nodejs 18.18.2-r0</title>
    <updated>2026-10-02T22:09:31.648595+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> CleanStart: nodejs</p>
<p>Package nodejs version 18.18.2-r0 fixes 3 vulnerabilities: CVE-2023-45143, CVE-2023-38552, CVE-2023-39333</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-fi53720"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-258453</id>
    <title>EUVD-2026-258453</title>
    <updated>2026-10-02T22:09:31.648613+00:00</updated>
    <content>EUVD-2026-258453</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-258453"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-38552</id>
    <title>fkie_cve-2023-38552</title>
    <updated>2026-10-02T22:09:31.648624+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to the node's policy implementation, thus effectively disabling the integrity check.
Impacts:
This vulnerability affects all users using the experimental policy mechanism in all active release lines: 18.x and, 20.x.
Please note that at the time this CVE was issued, the policy mechanism is an experimental feature of Node.js.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-38552"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-x39v-frq9-5hh8</id>
    <title>GHSA-x39v-frq9-5hh8</title>
    <updated>2026-10-02T22:09:31.648646+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to the node's policy implementation, thus effectively disabling the integrity check.
Impacts:
This vulnerability affects all users using the experimental policy mechanism in all active release lines: 18.x and, 20.x.
Please note that at the time this CVE was issued, the policy mechanism is an experimental feature of Node.js.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-x39v-frq9-5hh8"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-38552</id>
    <title>gsd-2023-38552</title>
    <updated>2026-10-02T22:09:31.648662+00:00</updated>
    <content>gsd-2023-38552</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-38552"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/icsa-24-319-08</id>
    <title>ICSA-24-319-08 — Siemens SINEC INS</title>
    <updated>2026-10-02T22:09:31.648671+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence. Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be mislead by removing adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications. The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated. As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue. The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of available stack memory, causing `named` to terminate unexpectedly. Since each incoming control cha…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/icsa-24-319-08"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2023-38552</id>
    <title>msrc_CVE-2023-38552 — When the Node.js policy feature checks the integrity of a resource against a trusted manifest the application can inter…</title>
    <updated>2026-10-02T22:09:31.648867+00:00</updated>
    <content>msrc_CVE-2023-38552</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2023-38552"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13337-1</id>
    <title>openSUSE-SU-2024:13337-1 — corepack20-20.8.1-1.1 on GA media</title>
    <updated>2026-10-02T22:09:31.648885+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>corepack20-20.8.1-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2024:13337-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2023:4132-1</id>
    <title>SUSE-SU-2023:4132-1 — Security update for nodejs18</title>
    <updated>2026-10-02T22:09:31.648902+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for nodejs18</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2023:4132-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-38552</id>
    <title>UBUNTU-CVE-2023-38552</title>
    <updated>2026-10-02T22:09:31.648917+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:22.04:LTS: nodejs</p>
<p>When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to the node's policy implementation, thus effectively disabling the integrity check. Impacts: This vulnerability affects all users using the experimental policy mechanism in all active release lines: 18.x and, 20.x. Please note that at the time this CVE was issued, the policy mechanism is an experimental feature of Node.js.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-38552"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2655</id>
    <title>WID-SEC-W-2023-2655 — Node.js: Mehrere Schwachstellen</title>
    <updated>2026-10-02T22:09:31.648938+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter oder anonymer Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um beliebigen Programmcode auszuführen, Informationen offenzulegen, einen Denial of Service Zustand herbeizuführen oder Sicherheitsvorkehrungen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2655"/>
  </entry>
</feed>
