dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-32914

HIGH · 7.4 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 →
83/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_multipart_new_from_message() function is vulnerable to an out-of-bounds read. This flaw allows a malicious HTTP client to induce the libsoup server to read out of bounds.

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

The soup_multipart_new_from_message() function in libsoup lacks proper boundary validation when parsing HTTP multipart messages, allowing a malicious client to send crafted requests that cause the server to read memory outside allocated buffers. This out-of-bounds read could leak sensitive server memory contents to the attacker.

MitigationUpdate libsoup to the patched version that adds proper bounds checking in soup_multipart_new_from_message(). Until a patch is available, implement request size limits and validate multipart message structure before passing to the vulnerable function.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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: find / -name 'libsoup*' 2>/dev/null, or check package manager: dpkg -l | grep libsoup (Debian) or rpm -qa | grep libsoup (RHEL)
    Affected if libsoup libraries are present on the system
  2. Determine installed libsoup version
    Run: pkg-config --modversion libsoup-3.0 or dpkg -l | grep libsoup or rpm -q libsoup, depending on your system
    Affected if The installed version matches or falls within the affected version range (prior to patch)
  3. Verify multipart HTTP handling is enabled
    Check application configuration or code for usage of multipart message parsing: grep -r 'multipart' /path/to/application/config or review code for calls to soup_multipart_* functions
    Affected if The server or application is configured to accept and parse HTTP multipart messages from clients
  4. Confirm soup_multipart_new_from_message is reachable
    Review application source code or runtime behavior: grep -r 'soup_multipart_new_from_message' source/ or use ltrace/strace to trace function calls if binary-only
    Affected if The vulnerable function soup_multipart_new_from_message is being called to process incoming HTTP requests

The system is affected if it runs an unpatched libsoup version that parses HTTP multipart messages via soup_multipart_new_from_message, allowing an attacker to trigger out-of-bounds reads by sending crafted requests.

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 that adds proper bounds checking in soup_multipart_new_from_message(). Until a patch is available, implement request size limits and validate multipart message structure before passing to the vulnerable function.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32914 — 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-32914 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