Skip to main content
VulnerabilityPublished Updated

CVE-2026-15709: libsoup's WebSocket implementation · CWE-409

Source GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-15709· High 7.5

Not known to be exploited · CVSS 7.5 High : patch Red Hat Enterprise Linux 10 soon.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Enterprise Linux 10libsoup3Affected–Fixed in–
Red Hat Enterprise Linux 10.0 Extended Update Supportlibsoup3Affected–Fixed in–
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update SupportlibsoupAffected–Fixed in–
Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-OnlibsoupAffected–Fixed in–
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update SupportlibsoupAffected–Fixed in–
Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-OnlibsoupAffected–Fixed in–

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

References

Community reviews

Loading reviews…