dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2025-32913

HIGH · 7.5 CVSS v3.1 Published 2025-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

libsoup's soup_message_headers_get_content_disposition() function contains a NULL pointer dereference vulnerability when parsing maliciously crafted HTTP Content-Disposition headers. An attacker controlling an HTTP peer can crash any libsoup-based client or server by sending a specially crafted response that triggers the dereference.

MitigationUpdate libsoup to the patched version containing the fix. If immediate patching is not possible, avoid processing Content-Disposition headers from untrusted HTTP peers or implement input validation as a defensive measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if libsoup is in use
    Search for libsoup libraries in the system: 'ldd /path/to/your/application | grep libsoup' or check package manager: 'dpkg -l | grep libsoup' or 'rpm -qa | grep libsoup'
    Affected if libsoup libraries are present on the system
  2. Determine installed libsoup version
    Run 'pkg-config --modversion libsoup-3.0' or check package info: 'dpkg -l | grep libsoup' or 'rpm -qi libsoup3'
    Affected if The returned version is older than the patched version containing the fix for CVE-2025-32913
  3. Identify applications using libsoup
    Review application dependencies: check /usr/lib/x86_64-linux-gnu/libsoup* or scan application binaries with 'ldd' to find which processes link against libsoup
    Affected if Any production application or service links against libsoup and processes HTTP responses
  4. Verify if application handles Content-Disposition headers
    Review application source code or configuration for usage of soup_message_headers_get_content_disposition() function or inspection of HTTP header handling code
    Affected if Application parses or processes Content-Disposition headers from HTTP responses
  5. Assess trust boundary of HTTP peers
    Determine whether the application connects to untrusted HTTP servers or accepts responses from potentially malicious peers
    Affected if Application processes HTTP responses from untrusted or attacker-controlled network peers

You are affected if your system runs any libsoup-based application that parses Content-Disposition headers from untrusted HTTP peers and the installed libsoup version predates the CVE-2025-32913 fix.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libsoup to the patched version containing the fix. If immediate patching is not possible, avoid processing Content-Disposition headers from untrusted HTTP peers or implement input validation as a defensive measure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32913 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data