<?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>Sat, 03 Oct 2026 16:04:02 +0000</lastBuildDate>
    <item>
      <title>certfr-2024-avi-0757 — De multiples vulnérabilités ont été découvertes dans les produits Siemens. Certaines d'entre elles permettent à un atta…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0757</link>
      <description>certfr-2024-avi-0757</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0757</guid>
    </item>
    <item>
      <title>EUVD-2026-161239</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-161239</link>
      <description>EUVD-2026-161239</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-161239</guid>
    </item>
    <item>
      <title>fkie_cve-2024-38355</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-38355</link>
      <description>&lt;p&gt;Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io@4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the &amp;#34;error&amp;#34; event to catch these errors.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io@4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the &amp;#34;error&amp;#34; event to catch these errors.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-38355</guid>
    </item>
    <item>
      <title>GHSA-25hc-qcg6-38wj — socket.io has an unhandled 'error' event</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-25hc-qcg6-38wj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: socket.io&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process.&lt;/p&gt;
&lt;p&gt;```
node:events:502
    throw err; // Unhandled &amp;#39;error&amp;#39; event
    ^&lt;/p&gt;
&lt;p&gt;Error [ERR_UNHANDLED_ERROR]: Unhandled error. (undefined)
    at new NodeError (node:internal/errors:405:5)
    at Socket.emit (node:events:500:17)
    at /myapp/node_modules/socket.io/lib/socket.js:531:14
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
  code: &amp;#39;ERR_UNHANDLED_ERROR&amp;#39;,
  context: undefined
}
```&lt;/p&gt;
&lt;p&gt;### Affected versions&lt;/p&gt;
&lt;p&gt;| Version range    | Needs minor update?                            |
|------------------|------------------------------------------------|
| `4.6.2...latest` | Nothing to do               |
| `3.0.0...4.6.1`  | Please upgrade to `socket.io@4.6.2` (at least) |
| `2.3.0...2.5.0`  | Please upgrade to `socket.io@2.5.1`            |&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This issue is fixed by https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115, included in `socket.io@4.6.2` (released in May 2023).&lt;/p&gt;
&lt;p&gt;The fix was backported in the 2.x branch today: https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;As a workaround for the affected versions of the `socket.io` package, you can attach a listener for the &amp;#34;error&amp;#34; event:&lt;/p&gt;
&lt;p&gt;```js
io.on(&amp;#34;connection&amp;#34;, (socket) =&amp;gt; {
  socket.on(&amp;#34;error&amp;#34;, () =&amp;gt; {
    // ...
  });
});
```&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: socket.io&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process.&lt;/p&gt;
&lt;p&gt;```
node:events:502
    throw err; // Unhandled &amp;#39;error&amp;#39; event
    ^&lt;/p&gt;
&lt;p&gt;Error [ERR_UNHANDLED_ERROR]: Unhandled error. (undefined)
    at new NodeError (node:internal/errors:405:5)
    at Socket.emit (node:events:500:17)
    at /myapp/node_modules/socket.io/lib/socket.js:531:14
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
  code: &amp;#39;ERR_UNHANDLED_ERROR&amp;#39;,
  context: undefined
}
```&lt;/p&gt;
&lt;p&gt;### Affected versions&lt;/p&gt;
&lt;p&gt;| Version range    | Needs minor update?                            |
|------------------|------------------------------------------------|
| `4.6.2...latest` | Nothing to do               |
| `3.0.0...4.6.1`  | Please upgrade to `socket.io@4.6.2` (at least) |
| `2.3.0...2.5.0`  | Please upgrade to `socket.io@2.5.1`            |&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This issue is fixed by https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f07640336115, included in `socket.io@4.6.2` (released in May 2023).&lt;/p&gt;
&lt;p&gt;The fix was backported in the 2.x branch today: https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc41a828119c&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;As a workaround for the affected versions of the `socket.io` package, you can attach a listener for the &amp;#34;error&amp;#34; event:&lt;/p&gt;
&lt;p&gt;```js
io.on(&amp;#34;connection&amp;#34;, (socket) =&amp;gt; {
  socket.on(&amp;#34;error&amp;#34;, () =&amp;gt; {
    // ...
  });
});
```&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-25hc-qcg6-38wj</guid>
    </item>
    <item>
      <title>ICSA-24-256-08 — Siemens Industrial Products</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-24-256-08</link>
      <description>&lt;p&gt;Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io@4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the &amp;#34;error&amp;#34; event to catch these errors.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io@4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the &amp;#34;error&amp;#34; event to catch these errors.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-24-256-08</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3771-1 — Security update for pgadmin4</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3771-1</link>
      <description>&lt;p&gt;Security update for pgadmin4&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for pgadmin4&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:3771-1</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2091 — Siemens SIMATIC WinCC: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2091</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Siemens SIMATIC WinCC ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Siemens SIMATIC WinCC ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2091</guid>
    </item>
  </channel>
</rss>
