https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 16:58:14 +0000 https://cve.radiocsirt.org/vuln/cleanstart-2026-eu00318 <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> <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> https://cve.radiocsirt.org/vuln/cleanstart-2026-eu00318 https://cve.radiocsirt.org/vuln/euvd-2026-339036 EUVD-2026-339036 https://cve.radiocsirt.org/vuln/euvd-2026-339036 https://cve.radiocsirt.org/vuln/fkie_cve-2026-54466 <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> <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> https://cve.radiocsirt.org/vuln/fkie_cve-2026-54466 https://cve.radiocsirt.org/vuln/ghsa-xv26-6w52-cph6 <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> <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> https://cve.radiocsirt.org/vuln/ghsa-xv26-6w52-cph6 https://cve.radiocsirt.org/vuln/oesa-2026-3212 <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> <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> https://cve.radiocsirt.org/vuln/oesa-2026-3212 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11680-1 <p>agama-web-ui-24+0.a836cced5-52.1 on GA media</p> <p>agama-web-ui-24+0.a836cced5-52.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11680-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54466 <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> <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> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54466 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3204 <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> <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> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3204