# CVE-2026-1760: Libsoup: soupserver: denial of service via http request smuggling

> Remote attackers can cause denial of service in applications using Libsoup by exploiting HTTP request smuggling via crafted chunked requests.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 2 Feb 2026
- **Updated:** 19 Mar 2026
- **Also known as:** AZL-77618, AZL-77622, DEBIAN-CVE-2026-1760, ECHO-0d17-9796-549f, GHSA-58g3-53qw-g6m8, UBUNTU-CVE-2026-1760

## What is CVE-2026-1760?

CVE-2026-1760 is a medium-severity 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 SoupServer. This HTTP request smuggling vulnerability occurs because SoupServer improperly handles requests that combine Transfer-Encoding: chunked and Connection: keep-alive headers. A remote, unauthenticated client can exploit this by sending specially crafted requests, causing SoupServer to fail to close the connection as required by RFC 9112. This allows the attacker to smuggle additional requests over the persistent connection, leading to unintended request processing and potential denial-of-service (DoS) conditions.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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


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

Upgrade to a fixed version.

## Is CVE-2026-1760 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1760 is a medium-severity 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-1760 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-1760/ (Markdown: https://insights.sbomify.com/CVE-2026-1760/index.md)
```

## Sources

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

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