---
id: CVE-2026-1536
title: >-
  Libsoup: libsoup: http header injection or response splitting via crlf
  injection in content-disposition header
summary: >-
  A flaw was found in libsoup. An attacker who can control the input for the
  Content-Disposition header can inject CRLF (Carriage Return Line Feed)
  sequences into the header value. These sequences are then interpreted verbatim
  when the HTT…
severity: medium
cvss: 5.8
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N'
cvssSource: cna
cwe:
  - CWE-93
vendor: Red Hat
product: libsoup3
affected:
  - libsoup3 (all versions)
  - libsoup (all versions)
  - libsoup (all versions)
  - libsoup (all versions)
  - libsoup (all versions)
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-01-28T16:10:03.699999Z'
published: '2026-01-28'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T16:40:34.334Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-1536'
references:
  - url: 'https://access.redhat.com/security/cve/CVE-2026-1536'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2433834'
    label: RHBZ#2433834
  - url: 'https://gitlab.gnome.org/GNOME/libsoup/-/issues/486'
tags:
  - cve.org
epss: 0.00344
epssPercentile: 0.281
ingestedAt: '2026-11-05T22:38:31.377Z'
---

## Overview

A flaw was found in libsoup. An attacker who can control the input for the Content-Disposition header can inject CRLF (Carriage Return Line Feed) sequences into the header value. These sequences are then interpreted verbatim when the HTTP request or response is constructed, allowing arbitrary HTTP headers to be injected. This vulnerability can lead to HTTP header injection or HTTP response splitting without requiring authentication or user interaction.

## Affected

- `libsoup3 (all versions)`
- `libsoup (all versions)`
- `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 do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.