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).
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alma_linux | — | Upgrade libsoup-develUpgrade libsoup | Oct 11, 2026 | Sep 16, 2026 |
| Amazon_linux_2023 | — | Upgrade libsoup3-debuginfoUpgrade libsoup-debugsourceUpgrade libsoup3-debugsourceUpgrade libsoup3-develUpgrade libsoup-develUpgrade libsoup3-docUpgrade libsoup-debuginfoUpgrade libsoup3Upgrade libsoup-docUpgrade libsoup | Sep 30, 2026 | Jul 14, 2026 |
| Oracle_linux | — | Upgrade libsoup-develUpgrade libsoupUpgrade libsoup3Upgrade libsoup3-develUpgrade libsoup3-doc | Oct 22, 2026 | Jul 14, 2026 |
| Redhat_linux | — | No solution existsUpgrade libsoup-debugsourceUpgrade libsoup3-debugsourceUpgrade libsoup-develUpgrade libsoup3-docUpgrade libsoupUpgrade libsoup3-develUpgrade libsoup3-debuginfoUpgrade libsoup3Upgrade libsoup-debuginfo | Jul 17, 2026 | Jul 14, 2026 |
| Rocky_linux | — | Upgrade libsoupUpgrade libsoup-develUpgrade libsoup-debuginfoUpgrade libsoup-debugsource | Sep 18, 2026 | Sep 17, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub