CVE-2026-15714
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 · uneditedAn 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.
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 confidenceAn out-of-bounds read vulnerability exists in libsoup's multipart processing within the soup_multipart_input_stream_read_headers() function. The function fails to validate the size of incoming multipart boundary strings, allowing a crafted HTTP response with an oversized boundary parameter to read beyond allocated buffer bounds. A remote, unauthenticated attacker can exploit this to cause denial of service or leak memory fragments.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if libsoup is installedRun 'pkg-config --modversion libsoup-3.0' or 'pkg-config --modversion libsoup-2.4' to check the installed version. On Debian-based systems, also check 'dpkg -l | grep libsoup'.Affected if libsoup is present and the version is lower than the patched version containing boundary size validation fix in soup_multipart_input_stream_read_headers().
-
Determine if multipart HTTP responses are processedInspect application code or runtime behavior to see if it handles multipart/form-data or multipart/related HTTP responses using libsoup's soup_multipart_input_stream API.Affected if The application processes multipart HTTP responses through libsoup, enabling the vulnerable code path in soup_multipart_input_stream_read_headers().
-
Inspect HTTP response handling for boundary parameter usageUse network tracing (e.g., Wireshark) or application logs to observe if HTTP responses contain Content-Type headers with multipart boundary parameters.Affected if The application receives HTTP responses with multipart boundary parameters, which triggers the vulnerable function without size validation.
-
Check for crashes or memory anomalies in multipart processingReview application logs, crash reports, or memory dumps for indicators of out-of-bounds read errors occurring during multipart header parsing.Affected if Crashes or abnormal memory reads occur specifically when processing multipart response headers, indicating the vulnerability may be triggered.
A user is affected if libsoup is installed with an unpatched version that lacks boundary size validation AND the application processes multipart HTTP responses containing boundary parameters.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpdate libsoup to the latest version containing the boundary size validation fix. Until a patch is available, implement input validation at the application layer to reject HTTP responses with boundary parameters exceeding expected maximum lengths.
Fixed libsoup version as specified in distribution security advisory (e.g., RHEL errata)
- 1. Identify the exact version of libsoup currently installed in your environment using your system's package manager (e.g., rpm -q libsoup for RHEL/Fedora, dpkg -l libsoup for Debian/Ubuntu).
- 2. Check the GNOME GitLab libsoup repository (gitlab.gnome.org/GNOME/libsoup) for commits addressing the boundary validation issue in soup-multipart-input-stream.c.
- 3. Consult Red Hat's bugzilla (bugzilla.redhat.com) for CVE-2026-15714 to obtain the specific fixed version for RHEL-based distributions.
- 4. Upgrade to the fixed version of libsoup provided by your distribution's security advisories.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15714 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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