9307 matches found
ROOT-APP-MAVEN-CVE-2025-41254 CVE-2025-41254 in org.springframework:spring-websocket - Patched by Root
Root has patched CVE-2025-41254 in the org.springframework:spring-websocket package for Root:Maven. Multiple fixed versions available...
CVE-2026-101881 OpenClaw Windows Node before 2026.7.1 Denial of Service
OpenClaw Windows Node before 2026.7.1 contains an allocation of resources without limits vulnerability in the gateway WebSocket transport that allows connected gateways to exhaust node memory. Attackers can send an unending sequence of WebSocket continuation frames without EndOfMessage to cause...
CVE-2026-101881
The OpenClaw Windows Node software, specifically versions before 2026.7.1 , is vulnerable to a Denial of Service (DoS) condition. The root cause is an allocation of resources without limits within the gateway WebSocket transport . An attacker can exploit this by sending an unending sequence of We...
EUVD-2026-90254
OpenClaw Windows Node before 2026.7.1 contains an allocation of resources without limits vulnerability in the gateway WebSocket transport that allows connected gateways to exhaust node memory. Attackers can send an unending sequence of WebSocket continuation frames without EndOfMessage to cause...
CVE-2026-101881 OpenClaw Windows Node before 2026.7.1 Denial of Service
OpenClaw Windows Node before 2026.7.1 contains an allocation of resources without limits vulnerability in the gateway WebSocket transport that allows connected gateways to exhaust node memory. Attackers can send an unending sequence of WebSocket continuation frames without EndOfMessage to cause...
CVE-2026-101881 OpenClaw Windows Node before 2026.7.1 Denial of Service
OpenClaw Windows Node before 2026.7.1 contains an allocation of resources without limits vulnerability in the gateway WebSocket transport that allows connected gateways to exhaust node memory. Attackers can send an unending sequence of WebSocket continuation frames without EndOfMessage to cause...
CVE-2026-103472
restbed through 5.0.0 accepts WebSocket frames with declared payload lengths up to 2^63 bytes and buffers the payload without size limits in an unbounded stream buffer. Remote unauthenticated attackers can declare large frame sizes and stream payload data to exhaust server memory, causing denial ...
SUSE-SU-2026:23985-1 Security update for libtcnative-1-0, libtcnative-2-0, tomcat, tomcat10, tomcat11
This update for libtcnative-1-0, libtcnative-2-0, tomcat, tomcat10, tomcat11 fixes the following issues: Security issues fixed: - CVE-2026-73581: OpenSSL and OpenSSL-FFM TLS implementations ignore CRLs when certificate uses a keystore bsc1282631. - CVE-2026-75973: improper authentication when...
CVE-2026-103472 restbed through 5.0.0 WebSocket Memory Exhaustion via Unbounded Frame Buffering
restbed through 5.0.0 accepts WebSocket frames with declared payload lengths up to 2^63 bytes and buffers the payload without size limits in an unbounded stream buffer. Remote unauthenticated attackers can declare large frame sizes and stream payload data to exhaust server memory, causing denial ...
EUVD-2026-90203
restbed through 5.0.0 accepts WebSocket frames with declared payload lengths up to 2^63 bytes and buffers the payload without size limits in an unbounded stream buffer. Remote unauthenticated attackers can declare large frame sizes and stream payload data to exhaust server memory, causing denial ...
CVE-2026-103472 restbed through 5.0.0 WebSocket Memory Exhaustion via Unbounded Frame Buffering
restbed through 5.0.0 accepts WebSocket frames with declared payload lengths up to 2^63 bytes and buffers the payload without size limits in an unbounded stream buffer. Remote unauthenticated attackers can declare large frame sizes and stream payload data to exhaust server memory, causing denial ...
CVE-2026-103472
The restbed library (versions through 5.0.0 ) is vulnerable to a memory exhaustion issue within its WebSocket implementation. The root cause is that the library accepts WebSocket frames with declared payload lengths up to 2^63 bytes and buffers them in an unbounded stream buffer without size limi...
CVE-2026-103472 restbed through 5.0.0 WebSocket Memory Exhaustion via Unbounded Frame Buffering
restbed through 5.0.0 accepts WebSocket frames with declared payload lengths up to 2^63 bytes and buffers the payload without size limits in an unbounded stream buffer. Remote unauthenticated attackers can declare large frame sizes and stream payload data to exhaust server memory, causing denial ...
CVE-2026-102717
MQTT WebSocket setter ABI mismatch may disclose memory or cause a crash...
SUSE CVE-2026-102556
A flaw was found in libsoup. When handling an incoming WebSocket Pong frame, SoupWebsocketConnection emitted the ::pong signal with a GByteArray pointer even though the signal is declared to pass a GBytes. Applications connecting a handler that follows the documented GBytes API can trigger heap...
SUSE CVE-2026-102557
A flaw was found in libsoup. When reassembling fragmented WebSocket messages into a GByteArray, libsoup did not adequately cap total message size against the limits of the underlying buffer type. A remote peer could send fragments that caused size truncation while the implementation still used th...
SUSE CVE-2026-102559
A flaw was found in libsoup. When constructing a masked WebSocket client frame for a very large outgoing payload, size values passed to GByteArray allocation APIs could be truncated while the masking routine still used the full length, causing a heap buffer overflow...
SUSE CVE-2026-102560
A flaw was found in libsoup. When the permessage-deflate WebSocket extension compresses a very large outgoing message, truncated size calculations used for GByteArray growth could wrap, causing zlib to write past the allocated buffer and resulting in a heap buffer overflow...
CVE-2026-102717
An ABI mismatch in the MQTT WebSocket setter can lead to memory disclosure or a system crash . While the documents provide a high-level description of the vulnerability and its potential impact on availability, specific affected software versions, root causes, or remediation steps are not explici...