Libsoup: null pointer dereference in soup_message_headers_get_content_disposition when "filename" parameter is present, but has no value in content-disposition header (CVE-2025-32913)

Why this deserves its current priority

CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps libsoup (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
libsoupgeneric	>=0 <3.6.2	3.6.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for libsoup.
Review the reported fix. Source-reported workaround: Currently, no mitigation is available for this vulnerability.

Evidence timeline and material changes

Published upstream
Apr 14, 2025
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jun 25, 2026

Sources and claim methodology

Upstream source description

A flaw was found in libsoup, where the soup_message_headers_get_content_disposition() function is vulnerable to a NULL pointer dereference. This flaw allows a malicious HTTP peer to crash a libsoup client or server that uses this function.

Quoted source text, attributed separately from HOL analysis.

Libsoup: null pointer dereference in soup_message_headers_get_content_disposition when "filename" parameter is present, but has no value in content-disposition headerCVE-2025-32913