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
Configurations
No configuration.
History
15 Jul 2026, 14:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://gitlab.gnome.org/GNOME/libsoup/-/issues/511 - |
14 Jul 2026, 20:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-07-14 20:16
Updated : 2026-07-15 18:20
NVD link : CVE-2026-15709
Mitre link : CVE-2026-15709
CVE.ORG link : CVE-2026-15709
JSON object : View
Products Affected
No product.
CWE
CWE-409
Improper Handling of Highly Compressed Data (Data Amplification)
