https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-10-10T10:10:42.333596+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/fkie_cve-2026-102557 fkie_cve-2026-102557 2026-10-10T10:10:42.427876+00:00

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.

 https://vulnerability.circl.lu/vuln/ghsa-fc8r-xmg7-v58h GHSA-fc8r-xmg7-v58h 2026-10-10T10:10:42.428023+00:00

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.

 https://vulnerability.circl.lu/vuln/msrc_cve-2026-102557 msrc_CVE-2026-102557 — Libsoup: libsoup: heap buffer overflow during websocket message reassembly 2026-10-10T10:10:42.428052+00:00 msrc_CVE-2026-102557 https://vulnerability.circl.lu/vuln/opensuse-su-2026:12084-1 openSUSE-SU-2026:12084-1 — libsoup-2_4-1-2.74.3-24.1 on GA media 2026-10-10T10:10:42.428077+00:00

libsoup-2_4-1-2.74.3-24.1 on GA media

 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-102557 UBUNTU-CVE-2026-102557 2026-10-10T10:10:42.428106+00:00

Affected: Ubuntu:Pro:16.04:LTS: libsoup2.4, Ubuntu:Pro:18.04:LTS: libsoup2.4, Ubuntu:Pro:20.04:LTS: libsoup2.4, Ubuntu:22.04:LTS: libsoup2.4, Ubuntu:Pro:22.04:LTS: libsoup3, Ubuntu:24.04:LTS: libsoup2.4, Ubuntu:24.04:LTS: libsoup3, Ubuntu:26.04:LTS: libsoup3, Ubuntu:Pro:26.04:LTS: libsoup2.4

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.