<?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-05T04:51:56.472333+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/cleanstart-2026-eu00318</id>
    <title>Withdrawn: CLEANSTART-2026-EU00318 — Security fixes in argo-workflows 3.7.17-r1</title>
    <updated>2026-10-05T04:51:56.596840+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: argo-workflows</p>
<p>Package argo-workflows version 3.7.17-r1 fixes 16 vulnerabilities: ghsa-3ppc-4f35-3m26, ghsa-7r86-cg39-jmmj, ghsa-23c5-xmqv-rm74, ghsa-xv26-6w52-cph6, ghsa-q3j6-qgpj-74h6...</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-eu00318"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-339036</id>
    <title>EUVD-2026-339036</title>
    <updated>2026-10-05T04:51:56.596895+00:00</updated>
    <content>EUVD-2026-339036</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-339036"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54466</id>
    <title>fkie_cve-2026-54466</title>
    <updated>2026-10-05T04:51:56.596912+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-54466"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xv26-6w52-cph6</id>
    <title>GHSA-xv26-6w52-cph6 — websocket-driver: Message corruption via abuse of protocol length headers</title>
    <updated>2026-10-05T04:51:56.596938+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: websocket-driver</p>
<p>### Impact</p>
<p>The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values `0x80` or above, a client can make the server parse these bytes into an ever-growing integer. Since JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly.</p>
<p>### Patches</p>
<p>The issue has been patched in version 0.7.5 by rejecting the message if the length header exceeds the configured maximum message length. All users should upgrade to this version.</p>
<p>### Workarounds</p>
<p>No known workarounds exist.</p>
<p>### Acknowledgements</p>
<p>This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xv26-6w52-cph6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-3212</id>
    <title>OESA-2026-3212 — nodejs-websocket-driver security update</title>
    <updated>2026-10-05T04:51:56.596969+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: nodejs-websocket-driver, openEuler:24.03-LTS-SP1: nodejs-websocket-driver, openEuler:24.03-LTS-SP3: nodejs-websocket-driver, openEuler:24.03-LTS-SP4: nodejs-websocket-driver, openEuler:20.03-LTS-SP4: nodejs-websocket-driver</p>
<p>.

Security Fix(es):</p>
<p>websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.(CVE-2026-54466)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-3212"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11680-1</id>
    <title>openSUSE-SU-2026:11680-1 — agama-web-ui-24+0.a836cced5-52.1 on GA media</title>
    <updated>2026-10-05T04:51:56.597000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>agama-web-ui-24+0.a836cced5-52.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:11680-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54466</id>
    <title>UBUNTU-CVE-2026-54466</title>
    <updated>2026-10-05T04:51:56.597029+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: node-websocket-driver, Ubuntu:18.04:LTS: node-websocket-driver, Ubuntu:20.04:LTS: node-websocket-driver, Ubuntu:22.04:LTS: node-websocket-driver, Ubuntu:24.04:LTS: node-websocket-driver, Ubuntu:26.04:LTS: node-websocket-driver</p>
<p>websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54466"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3204</id>
    <title>WID-SEC-W-2026-3204 — IBM App Connect Enterprise: Mehrere Schwachstellen</title>
    <updated>2026-10-05T04:51:56.597057+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um einen Denial of Service Angriff durchzuführen oder Daten zu manipulieren.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3204"/>
  </entry>
</feed>
