# CVE-2026-15714: Memory corruption in Red Hat Enterprise Linux 10

> A remote attacker can cause denial of service or read unauthorized memory via an oversized multipart boundary in libsoup.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** AZL-92405, DEBIAN-CVE-2026-15714, ECHO-d10b-a930-7882, GHSA-pr44-vh8f-w48v, UBUNTU-CVE-2026-15714

## What is CVE-2026-15714?

CVE-2026-15714 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-15714?


## How do I fix CVE-2026-15714?

Apply the vendor's patch.

## Is CVE-2026-15714 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15714 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15714 and fix it if it is affected.

What it is: CVE-2026-15714 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15714 exists.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15714/ (Markdown: https://insights.sbomify.com/CVE-2026-15714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15714
- OSV: https://osv.dev/vulnerability/CVE-2026-15714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15714/
Summaries are generated and may contain mistakes; the official description above is the record.