CVE-2025-32049
Published: 03 April 2025
Summary
CVE-2025-32049 is a high-severity Allocation of Resources Without Limits or Throttling (CWE-770) vulnerability. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 29.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
A flaw exists in the libsoup library's SoupWebsocketConnection component that permits acceptance of an arbitrarily large WebSocket message. This triggers uncontrolled memory allocation, resulting in a denial-of-service condition. The issue is tracked as CVE-2025-32049 with a CVSS 3.1 base score of 7.5 and is classified under CWE-770.
An unauthenticated remote attacker can exploit the vulnerability over the network by sending a crafted WebSocket message to any application using the affected libsoup websocket handling code, exhausting resources and disrupting service availability without requiring user interaction.
Multiple Red Hat Security Advisories (RHSA-2025:21657, RHSA-2025:8126, RHSA-2025:8128, RHSA-2025:8132, and RHSA-2025:8139) address the flaw through updated packages that enforce message-size limits or improved resource checks. The EPSS score rose from a low baseline of 0.0060 to a peak of 0.0156, indicating increased exploitation interest after public disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-9634
Vulnerability details
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).
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
This control implements explicit throttling on session allocation, addressing the weakness of allocating resources without limits.
Plan testing exercises resource allocation limits and throttling during simulated failures, directly addressing weaknesses that allow unbounded resource use.
Contingency plan updates ensure recovery strategies address unbounded resource allocation, making it harder for attackers to exploit lack of throttling to cause prolonged outages.
Provides continuity when unbounded resource allocation at the primary site leads to exhaustion and downtime.
Alternate services allow operations to continue when primary allocation of resources lacks limits or throttling.
Explicit planning of security-related actions requires defining limits, windows, and resource allocations, making allocation without throttling far less likely.
Measures of performance include tracking allocation behavior and throttling effectiveness, reducing the window for resource exhaustion attacks.
Imposes an inactivity-based limit on network resource allocation, throttling the number of concurrently held connections.