# CVE-2026-1761: Libsoup: stack-based buffer overflow in libsoup multipart response parsingmultipart http response

> Remote attackers can trigger a stack-based buffer overflow in libsoup via crafted multipart responses, leading to code execution or crashes in applications processing untrusted data.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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:** 2 Feb 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALSA-2026:2410, AZL-76697, AZL-76740, DEBIAN-CVE-2026-1761, ECHO-74b5-8029-1a64, GHSA-6j8r-j98h-9g9f, RHSA-2026:2410, RLSA-2026:2410, ROOT-OS-DEBIAN-12-CVE-2026-1761, ROOT-OS-DEBIAN-13-CVE-2026-1761, SUSE-SU-2026:0419-1, UBUNTU-CVE-2026-1761, openSUSE-SU-2026:20283-1

## What is CVE-2026-1761?

CVE-2026-1761 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 2 Feb 2026. 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. This stack-based buffer overflow vulnerability occurs during the parsing of multipart HTTP responses due to an incorrect length calculation. A remote attacker can exploit this by sending a specially crafted multipart HTTP response, which can lead to memory corruption. This issue may result in application crashes or arbitrary code execution in applications that process untrusted server responses, and it does not require authentication or user interaction.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsoup3-doc` | AlmaLinux:10 | All versions | 3.6.5-3.el10_1.10 |
| `libsoup3` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.10 |
| `libsoup3-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.10 |
| `libsoup3-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.10 |
| `libsoup3-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.10 |
| `libsoup3-doc` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.10 |
| `libsoup3` | Rocky Linux:10 | All versions | 0:3.6.5-3.el10_1.10 |
| `libsoup` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 2.62.2-5.29.1 |
| `libsoup` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.62.2-5.29.1 |
| `libsoup2` | openSUSE:Leap 16.0 | All versions | 2.74.3-160000.3.1 |

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

Apply the vendor's patch.

## Is CVE-2026-1761 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1761 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 2 Feb 2026. 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-2026-1761 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-2026-1761/ (Markdown: https://insights.sbomify.com/CVE-2026-1761/index.md)
```

## Sources

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

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