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.
CVE-2026-15713
MEDIUMPre-NVD 5.95.9—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.9 from GitHub Security Advisory published 2026-07-14. a secondary CVSS source baseline 5.9; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(high)
- EPSS
- 27.1%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026🔬 Proof of concept available. Patch available. Sources: redhat.
generic🟡 PoC Available
(#YWH-PGM9867-209) Information Disclosure and Cross-User Credential Leak in SoupSession through SoupCache:get_cacheability() in libsoup/cache/soup-cache.c via Header "`Authorization`and `Cache-Control: max-age=600`" with SOUP_CACHE_SHARED mode (#541) · Issues · GNOME / libsoup · GitLab
https://gitlab.gnome.org/GNOME/libsoup/-/work_items/541redhat
2499941 – (CVE-2026-15713) CVE-2026-15713 libsoup: SoupCache: libsoup: HTTP/2 frame window exhaustion remote denial of service via memory leak
https://bugzilla.redhat.com/show_bug.cgi?id=2499941Vendor Advisories for CVE-2026-15713(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 5× in last 7d / 5× 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 20:59 UTCEG score recompute
- 2026-07-15 20:59 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-14 20:02 UTCEG score recompute
- 2026-07-14 20:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-772
Frequently asked(5)
What is CVE-2026-15713?
CVE-2026-15713 is a medium vulnerability published on July 14, 2026. 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…
When was CVE-2026-15713 disclosed?
CVE-2026-15713 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15713 actively exploited?
CVE-2026-15713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15713?
CVE-2026-15713 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-15713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15713, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15713
Is Your Infrastructure Affected by CVE-2026-15713?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.