CVE-2026-15709: Libsoup2.4 · A flaw was found in libsoup's WebSocket implementation when using the permessage-deflate
Affects libsoup2.4Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 3 Nov 2026, 23:14 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10libsoup2.4pkg:deb/ubuntu/libsoup2.4?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10libsoup3pkg:deb/ubuntu/libsoup3?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlibsoup3pkg:deb/ubuntu/libsoup3?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu Pro 26.04 LTSlibsoup2.4pkg:deb/ubuntu/libsoup2.4?arch=source&distro=esm-apps/resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlibsoup2.4pkg:deb/ubuntu/libsoup2.4?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlibsoup3pkg:deb/ubuntu/libsoup3?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
A flaw was found in libsoup's WebSocket implementation when using the permessage-deflate extension. The extension's decompression loop (inflate()) processes data in chunks without enforcing an upper boundary limit on the output buffer size. While libsoup limits the incoming compressed frame size via max_incoming_payload_size, it fails to track or limit memory allocation during decompression. A separate check for decompressed size (max_total_message_size) exists but executes only after inflation is complete, and it is entirely disabled by default for client connections. A remote, unauthenticated attacker can exploit this by sending a small, highly compressed payload (a decompression bomb), causing unbounded memory allocation that triggers an Out-of-Memory (OOM) crash and a Denial of Service (DoS).
References
- ubuntu.com/security/CVE-2026-15709 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-15709 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-15709 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2499922 (opens in a new tab)
- gitlab.gnome.org/GNOME/libsoup/-/issues/511 (opens in a new tab)