---
id: CVE-2026-1760
title: 'Libsoup: soupserver: denial of service via http request smuggling'
summary: >-
  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 …
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'
cvssSource: cna
cwe:
  - CWE-444
vendor: Red Hat
product: libsoup3
affected:
  - libsoup3 (all versions)
  - libsoup
  - libsoup (all versions)
  - libsoup (all versions)
  - libsoup (all versions)
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-02-02T17:29:44.685159Z'
published: '2026-02-02'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T19:23:41.141Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-1760'
references:
  - url: 'https://access.redhat.com/security/cve/CVE-2026-1760'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2435951'
    label: RHBZ#2435951
  - url: 'https://gitlab.gnome.org/GNOME/libsoup/-/issues/475'
tags:
  - cve.org
epss: 0.00473
epssPercentile: 0.41035
ingestedAt: '2026-11-05T22:38:31.532Z'
---

## Overview

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.

## Affected

- `libsoup3 (all versions)`
- `libsoup`
- `libsoup (all versions)`
- `libsoup (all versions)`
- `libsoup (all versions)`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

### Workarounds

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.