dbcve.org
CWE-772Weakness · CWE-772

CVE-2026-15713

MEDIUM · 5.9 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Memory leak in libsoup's HTTP/2 implementation where stream state blocks fail to be released during cleanup under specific conditions (window exhaustion or stream resets). A remote attacker can trigger repeated stream allocation without proper deallocation, exhausting heap memory and causing OOM crashes.

MitigationUpdate libsoup to a patched version addressing the HTTP/2 memory leak. Implement network-level controls to limit exposure to untrusted HTTP/2 peers until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify libsoup installation and version
    Run 'pkg-config --modversion libsoup-3.0' or 'dpkg -l libsoup-3.0-1' or check your system's package manager for libsoup version
    Affected if libsoup version is present and falls within the unpatched version range for this vulnerability (check against vendor security advisories)
  2. Confirm HTTP/2 support is enabled
    Inspect application or system configuration for HTTP/2 enablement in libsoup clients/servers. Check environment variables like SOUP_HTTP2_ENABLE or application-specific settings that enable HTTP/2
    Affected if HTTP/2 protocol support is actively enabled in libsoup configuration or application settings
  3. Detect abnormal memory growth
    Monitor heap memory usage of processes using libsoup with HTTP/2 connections over time. Use tools like 'ps aux', 'top', or memory profiling to observe continuously growing memory not released during normal operation
    Affected if Processes using libsoup HTTP/2 show steadily increasing memory consumption that does not stabilize or decrease during idle periods, especially under active HTTP/2 traffic
  4. Review HTTP/2 stream state
    If application supports debugging, enable libsoup debug logging (SOUP_DEBUG) or check for stream state messages indicating unclean shutdowns, window exhaustion events, or stream reset sequences
    Affected if Logs or debug output show repeated stream allocation without corresponding cleanup under high-volume or reset conditions
  5. Check for OOM events
    Review system logs (dmesg, journalctl, syslog) for out-of-memory killer events or malloc failures occurring in libsoup-using applications
    Affected if System reports OOM kills or memory allocation failures in libsoup-dependent services handling HTTP/2 traffic

Your environment is affected if libsoup with HTTP/2 enabled is running an unpatched version and you observe abnormal memory growth or OOM events during HTTP/2 communication, particularly under conditions of stream resets or window exhaustion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libsoup to a patched version addressing the HTTP/2 memory leak. Implement network-level controls to limit exposure to untrusted HTTP/2 peers until the patch is applied.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15713 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data