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).
CVE-2026-15709
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EPSS
- 42.2%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026WebSocket Decompression Bomb (#511) · Issues · GNOME / libsoup · GitLab
https://gitlab.gnome.org/GNOME/libsoup/-/issues/5112499922 – (CVE-2026-15709) CVE-2026-15709 SoupWebsocketExtensionDeflate: libsoup: libsoup: WebSocket permessage-deflate Unbounded Decompression Remote Denial of Service
https://bugzilla.redhat.com/show_bug.cgi?id=2499922Vendor Advisories for CVE-2026-15709(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 22:24 UTCEG score recompute
- 2026-07-15 22:24 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 09:14 UTCEG score recompute
- 2026-07-15 09:14 UTCGHSA enrichment
- 2026-07-14 20:03 UTCEG score recompute
- 2026-07-14 20:01 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-15709?
When was CVE-2026-15709 disclosed?
Is CVE-2026-15709 actively exploited?
What is the CVSS score of CVE-2026-15709?
How do I remediate CVE-2026-15709?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15709
Is Your Infrastructure Affected by CVE-2026-15709?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.