dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-32049

HIGH · 7.5 CVSS v3.1 Published 2025-04-03
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. The SoupWebsocketConnection may accept a large WebSocket message, which may cause libsoup to allocate memory and lead to a denial of service (DoS).

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 SoupWebsocketConnection lacks proper bounds validation on incoming WebSocket messages, allowing clients to send excessively large messages that trigger unbounded memory allocation, resulting in resource exhaustion and denial of service.

MitigationImplement message size limits and input validation in the SoupWebsocketConnection handler to reject or truncate messages exceeding reasonable thresholds, and update to patched libsoup version when available.

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 libsoup installation
    Run 'pkg-config --modversion libsoup-3.0' or 'dpkg -l | grep libsoup' (Debian) / 'rpm -qa | grep libsoup' (RHEL) to find the installed libsoup version
    Affected if libsoup version is unknown or falls within an unpatched release range
  2. Verify WebSocket usage in application
    Search application code for '#include <libsoup/soup-websocket.h>' or 'SoupWebsocketConnection' usage, or inspect running processes that link against libsoup using 'ldd <executable> | grep libsoup'
    Affected if application or service uses SoupWebsocketConnection for WebSocket communication
  3. Check for message size limits
    Inspect application code or configuration for SoupWebsocketMessage size limit settings (e.g., SoupWebsocketConnection::max-incoming-packet-size property or equivalent limit enforcement)
    Affected if no explicit message size limits are configured or enforced on incoming WebSocket messages
  4. Monitor memory consumption under load
    During normal or test WebSocket operation, monitor process memory with 'ps aux | grep <process>' or 'top' to observe memory growth patterns when large messages are received
    Affected if memory grows unboundedly or fails to stabilize when processing large WebSocket payloads

Environment is affected if libsoup with WebSocket functionality is in use and no message size limits are enforced on SoupWebsocketConnection, allowing unbounded memory allocation from large incoming messages.

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

Implement message size limits and input validation in the SoupWebsocketConnection handler to reject or truncate messages exceeding reasonable thresholds, and update to patched libsoup version when available.

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-32049 — 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-32049 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