A heap buffer over-read vulnerability was discovered in libsoup's (versions: libsoup 3.0 to 3.7.0) HTTP/2 connection tracking framework. When the library processes an HTTP/2 GOAWAY frame, it improperly handles the "Additional Debug Data" payload by assuming the data stream is a safely NUL-terminated C-string. Because the parser lacks strict length-boundary verification before reading this data, a remote, unauthenticated attacker can intentionally send a malformed GOAWAY frame missing the appropriate null delimiter. This causes the library to read past the end of the allocated buffer, triggering an application crash that results in a denial of service (DoS), or potentially exposing fragments of memory contents.
CVE-2026-15712
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
- 39.3%
- 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-228) libsoup HTTP/2 GOAWAY Heap Buffer Over-Read via NUL-Terminated String Assumption (#540) · Issues · GNOME / libsoup · GitLab
https://gitlab.gnome.org/GNOME/libsoup/-/work_items/540redhat
2499939 – (CVE-2026-15712) CVE-2026-15712 SoupClientMessageIOHTTP2: libsoup3: libsoup: HTTP/2 GOAWAY frame parsing heap buffer over-read via invalid NUL-termination assumption
https://bugzilla.redhat.com/show_bug.cgi?id=2499939Vendor Advisories for CVE-2026-15712(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:08 UTCEG score recompute
- 2026-07-15 20:08 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-14 18:35 UTCEG score recompute
- 2026-07-14 18:35 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-125
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-2015-9290EG 9.8CRITICAL
- CVE-2016-10749EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2014-3180EG 9.1CRITICAL
- CVE-2014-1508EG 9.1EPSS 90%CRITICAL
- CVE-2016-5198NVD 8.8EG 9.0 KEVEPSS 98%HIGH
- CVE-2016-4523NVD 7.5EG 9.0 KEVEPSS 98%HIGH
Frequently asked(5)
What is CVE-2026-15712?
CVE-2026-15712 is a medium vulnerability published on July 14, 2026. A heap buffer over-read vulnerability was discovered in libsoup's (versions: libsoup 3.0 to 3.7.0) HTTP/2 connection tracking framework. When the library processes an HTTP/2 GOAWAY frame, it improperly handles the "Additional Debug Data" payload by assuming the data stream is a safely…
When was CVE-2026-15712 disclosed?
CVE-2026-15712 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-15712 actively exploited?
CVE-2026-15712 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15712?
CVE-2026-15712 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-15712?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15712, 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-15712
Is Your Infrastructure Affected by CVE-2026-15712?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.