# CVE-2025-2784: Libsoup: heap buffer over-read in `skip_insignificant_space` when sniffing content

> A heap buffer over-read in libsoup allows attackers to cause crashes or leak memory via crafted HTTP responses.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2025
- **Updated:** 30 Jun 2026
- **Also known as:** AZL-59535, AZL-59544, DEBIAN-CVE-2025-2784, GHSA-5qxx-2mqf-3v7g, JLSEC-2026-1280, UBUNTU-CVE-2025-2784

## What is CVE-2025-2784?

CVE-2025-2784 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in libsoup. The package is vulnerable to a heap buffer over-read when sniffing content via the skip_insight_whitespace() function. Libsoup clients may read one byte out-of-bounds in response to a crafted HTTP response by an HTTP server.

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

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

It affects 21 products.


Products: Gnome Libsoup, Redhat Codeready Linux Builder, Redhat Codeready Linux Builder for Arm64, Redhat Codeready Linux Builder for Arm64 Eus, Redhat Codeready Linux Builder for Ibm Z Systems, Redhat Codeready Linux Builder for Ibm Z Systems Eus, Redhat Codeready Linux Builder for Power Little Endian, Redhat Codeready Linux Builder for Power Little Endian Eus, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Arm 64, Redhat Enterprise Linux for Arm 64 Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server for Power Little Endian Update Services for Sap Solutions, Redhat Enterprise Linux Server Tus and 1 more.

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

Apply the vendor's patch.

## Is CVE-2025-2784 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2026-102556](https://insights.sbomify.com/CVE-2026-102556/): Libsoup: libsoup: heap buffer overflow from websocket pong signal type confusion (high 8.6)
- [CVE-2026-102557](https://insights.sbomify.com/CVE-2026-102557/): Libsoup: libsoup: heap buffer overflow during websocket message reassembly (high 8.6)
- [CVE-2026-102558](https://insights.sbomify.com/CVE-2026-102558/): Libsoup: libsoup: heap buffer overflow during websocket receive-buffer growth (high 8.6)
- [CVE-2026-102559](https://insights.sbomify.com/CVE-2026-102559/): Libsoup: libsoup: heap buffer overflow during websocket client-frame masking (high 8.6)
- [CVE-2026-102560](https://insights.sbomify.com/CVE-2026-102560/): Libsoup: libsoup: heap buffer overflow during outgoing permessage-deflate buffer growth (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2784 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 3 Apr 2025. 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-2025-2784 exists.

Affected product: Redhat Enterprise Linux. 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-2784/ (Markdown: https://insights.sbomify.com/CVE-2025-2784/index.md)
```

## Sources

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

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