Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-15713

libsoup: SoupCache: libsoup: HTTP/2 frame window exhaustion remote denial of service via memory leak

Overview

Published
14 Jul 2026
Modified
6 Nov 2026
Medium CVE
0 Registry packages
22 OS packages
9 Linux distributions
Yes Fix available

Description

A vulnerability was found in libsoup's HTTP/2 protocol implementation. The library fails to correctly release memory context blocks under specific stream termination conditions, such as when an HTTP/2 connection encounters window exhaustion or explicit stream resets. A remote, unauthenticated attacker acting as a malicious network peer can trick the connection engine into allocating stream states that are subsequently leaked during cleanup. Over a sustained period, this flaw allows the remote attacker to consume the system's heap allocations incrementally, triggering a denial of service (DoS) through an ultimate Out-of-Memory (OOM) application crash.

Source: OX vulnerability database

Severity

5.9 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-772

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 27 fixes

Red Hat 3 releases · 1 package

eol 1 affected 2
libsoup
Red Hat fixes for CVE-2026-15713
ReleasePackageFixed in
7 libsoup +1 eol
8 libsoup +1 affected
9 libsoup +1 affected

SUSE Linux Enterprise 6 releases · 2 packages

fixed 10
libsoup-2-4-1 libsoup-3-0-0
SUSE Linux Enterprise fixes for CVE-2026-15713
ReleasePackageFixed inAdvisory
12.5 libsoup-2-4-1 +4 2.62.2-5.49.1 SUSE-SU-2026:4690-1
15.4 libsoup-2-4-1 +3 2.74.3-150400.3.43.1 SUSE-SU-2026:4739-1
15.4 libsoup-3-0-0 +3 3.0.4-150400.3.55.1 SUSE-SU-2026:4616-1
15.5 libsoup-2-4-1 +3 2.74.3-150400.3.43.1 SUSE-SU-2026:4739-1
15.5 libsoup-3-0-0 +3 3.0.4-150400.3.55.1 SUSE-SU-2026:4616-1
15.6 libsoup-2-4-1 +3 2.74.3-150600.4.42.1 SUSE-SU-2026:4703-1

4 more rows

SUSE Linux Enterprise Micro 4 releases · 2 packages

fixed 4
libsoup-2-4-1 libsoup-3-0-0
SUSE Linux Enterprise Micro fixes for CVE-2026-15713
ReleasePackageFixed inAdvisory
5.3 libsoup-2-4-1 2.74.3-150400.3.43.1 SUSE-SU-2026:4739-1
5.4 libsoup-2-4-1 2.74.3-150400.3.43.1 SUSE-SU-2026:4739-1
5.5 libsoup-2-4-1 2.74.3-150400.3.43.1 SUSE-SU-2026:4739-1
6.0 libsoup-3-0-0 3.4.2-159998.1.1 SUSE-SU-2026:24368-1

amazon linux 1 release · 1 package

fixed 1
libsoup3
amazon linux fixes for CVE-2026-15713
ReleasePackageFixed in
2023 libsoup3 +4 3.7.2-1.amzn2023

debian 3 releases · 1 package

affected 3
libsoup2-4
debian fixes for CVE-2026-15713
ReleasePackageFixed in
11 libsoup2-4 affected
12 libsoup2-4 +1 affected
13 libsoup2-4 +1 affected

echo 1 release · 2 packages

affected 1 fixed 1
libsoup2-4 libsoup3
echo fixes for CVE-2026-15713
ReleasePackageFixed in
libsoup2-4 affected
libsoup3 3.6.6-1+e12

openSUSE 1 release · 2 packages

fixed 2
libsoup-2-4-1 libsoup-3-0-0
openSUSE fixes for CVE-2026-15713
ReleasePackageFixed inAdvisory
Tumbleweed libsoup-2-4-1 +6 2.74.3-25.1 openSUSE-SU-2026:12132-1
Tumbleweed libsoup-3-0-0 +6 3.8.1-1.1 openSUSE-SU-2026:12365-1

openSUSE Leap 1 release · 1 package

fixed 1
libsoup-3-0-0
openSUSE Leap fixes for CVE-2026-15713
ReleasePackageFixed inAdvisory
16.0 libsoup-3-0-0 +3 3.6.6-160000.5.1 openSUSE-SU-2026:22181-1

seal Red Hat 1 release · 1 package

fixed 1
libsoup
seal Red Hat fixes for CVE-2026-15713
ReleasePackageFixed in
7 libsoup +1 2.62.2-2.el7+sp999

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.