# CVE-2025-4969: Libsoup: off-by-one out-of-bounds read in find_boundary() in soup-multipart.c

> A remote attacker can trigger an out-of-bounds read in libsoup via crafted multipart HTTP messages, potentially causing crashes or leaking memory.

- **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:** 21 May 2025
- **Updated:** 30 Jun 2026
- **Also known as:** AZL-61945, AZL-61958, DEBIAN-CVE-2025-4969, GHSA-ff3g-4fq3-jf4p, ROOT-OS-DEBIAN-12-CVE-2025-4969, UBUNTU-CVE-2025-4969

## What is CVE-2025-4969?

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

### Official description

A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond its allocated memory boundaries (out-of-bounds read).

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

## Which versions are affected by CVE-2025-4969?


## How do I fix CVE-2025-4969?

Apply the vendor's patch.

## Is CVE-2025-4969 being exploited?

There is no known exploitation of CVE-2025-4969 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4969 and fix it if it is affected.

What it is: CVE-2025-4969 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4969 in the wild and no public exploit code.

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-2025-4969/ (Markdown: https://insights.sbomify.com/CVE-2025-4969/index.md)
```

## Sources

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

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