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).
References10
- access.redhat.com/errata/RHSA-2026:68234
- access.redhat.com/errata/RHSA-2026:68235
- access.redhat.com/errata/RHSA-2026:68612
- access.redhat.com/errata/RHSA-2026:69108
- access.redhat.com/errata/RHSA-2026:69297
- access.redhat.com/errata/RHSA-2026:69863
- access.redhat.com/errata/RHSA-2026:70598
- access.redhat.com/errata/RHSA-2026:70599
- access.redhat.com/errata/RHSA-2026:71389
- access.redhat.com/errata/RHSA-2026:98453
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 1% percentile: 62 · as of 15 November 2026
- CWE
- CWE-409
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.