CVE-2026-102557High· 8.6▾ TwilightA 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 c…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 47.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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 the full length, leading to heap corruption or a crash.
Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-102555High· 8.2Libsoup: libsoup: heap buffer overflow via uninitialized length in data-uri base64 decoding
CVE-2026-102558High· 8.6Libsoup: libsoup: heap buffer overflow during websocket receive-buffer growth
CVE-2026-102559High· 8.6Libsoup: libsoup: heap buffer overflow during websocket client-frame masking
CVE-2026-102560High· 8.6Libsoup: libsoup: heap buffer overflow during outgoing permessage-deflate buffer growth
CVE-2026-12478Medium· 4.8The fix for CVE-2026-0716 (commit 6ff7ef0, libsoup 3.6.6) placed the integer overflow guard inside the if (masked) block, leaving unmasked server-to-client frames unprotected
CVE-2026-102556High· 8.6A flaw was found in libsoup