CVE-2025-4948 | Libsoup: integer underflow in soup_multipart_new_from_message() leading to denial of service in libsoup

A flaw was found in the soup_multipart_new_from_message() function of the libsoup HTTP library, which is commonly used by GNOME and other applications to handle web communications. The issue occurs when the library processes specially crafted multipart messages. Due to improper validation, an internal calculation can go wrong, leading to an integer underflow. This can cause the program to access invalid memory and crash. As a result, any application or server using libsoup could be forced to exit unexpectedly, creating a denial-of-service (DoS) risk.

Published: 2025-05-19 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-4948 is rated Moderate Risk (57.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.99%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-4948

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-15 0.25% 0.99% +0.73%
2 2026-02-12 0.17% 0.25% +0.09%
3 2025-12-18 0.17%

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-4948

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-4948

OS Trackers for CVE-2025-4948

vendor priority summary link
debian not yet assigned CVE-2025-4948 not yet assigned priority: Debian including 2 source packages (libsoup2.4, libsoup3), 7 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 3. https://security-tracker.debian.org/tracker/CVE-2025-4948
redhat high https://access.redhat.com/security/cve/CVE-2025-4948
suse high CVE-2025-4948 severity important: SUSE including 57 source package names (curl-8.14.1-slfo.1.1_4.1, latest:curl-8.14.1-slfo.1.1_4.1, …), 216 product×package rows across 52 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (52 product lines)): Fixed 216. https://www.suse.com/security/cve/CVE-2025-4948/
ubuntu medium CVE-2025-4948 medium priority: Ubuntu including 2 source packages (libsoup2.4, libsoup3), 16 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): released 11, ignored 2, needs-triage 2, DNE 1. https://ubuntu.com/security/CVE-2025-4948

Affected software / configurations for CVE-2025-4948

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-4948

cvelogic Threat Intelligence