An out-of-bounds read vulnerability was found in libsoup's multipart processing subsystem. The flaw exists in the soup_multipart_input_stream_read_headers() function inside soup-multipart-input-stream.c, which does not adequately restrict or validate the size of incoming multipart boundary strings. When processing a crafted HTTP response containing a malformed or oversized boundary parameter, the internal stream reader reads past the allocated buffer bounds. A remote, unauthenticated attacker can exploit this behavior to cause a service denial (DoS) through application failure or potentially read fragments of unauthorized memory metadata.
CVE-2026-15714
Score 6.5 from GitHub Security Advisory published 2026-07-14. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EPSS
- 31.3%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026(#YWH-PGM9867-220) OOB Read on SoupSession through soup_multipart_input_stream_read_headers() in libsoup/soup-multipart-input-stream.c via large Multipart Boundary String (#542) · Issues · GNOME / libsoup · GitLab
https://gitlab.gnome.org/GNOME/libsoup/-/work_items/5422499942 – (CVE-2026-15714) CVE-2026-15714 libsoup: SoupMultipartInputStream: libsoup: Out-of-bounds read in soup_multipart_input_stream_read_headers via an oversized multipart boundary string
https://bugzilla.redhat.com/show_bug.cgi?id=2499942Vendor Advisories for CVE-2026-15714(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 18:04 UTCEG score recompute
- 2026-07-15 18:04 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-14 20:01 UTCEG score recompute
- 2026-07-14 20:01 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-15714?
When was CVE-2026-15714 disclosed?
Is CVE-2026-15714 actively exploited?
What is the CVSS score of CVE-2026-15714?
How do I remediate CVE-2026-15714?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15714
Is Your Infrastructure Affected by CVE-2026-15714?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.