Improper Handling of Highly Compressed Data (Data Amplification) Affecting libsoup package, versions *


Severity

Recommended
medium

Based on CentOS security rating.

Threat Intelligence

EPSS
0.55% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CENTOS7-LIBSOUP-17981383
  • published15 Jul 2026
  • disclosed14 Jul 2026

Introduced: 14 Jul 2026

NewCVE-2026-15709  (opens in a new tab)
CWE-409  (opens in a new tab)

How to fix?

There is no fixed version for Centos:7 libsoup.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsoup package and not the libsoup package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

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

CVSS Base Scores

version 3.1