CVE-2025-4969 | Libsoup: off-by-one out-of-bounds read in find_boundary() in soup-multipart.c

A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond its allocated memory boundaries (out-of-bounds read).

Published: 2025-05-21 Last update: 2026-05-06 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-4969 is rated Moderate Risk (51/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.66%). 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-4969

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-05-10 0.57% 0.66% +0.09%
2 2026-03-17 0.16% 0.57% +0.40%
3 2026-02-04 — 0.16% —

Full EPSS history (6 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L 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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 2.5 [email protected]

Weakness enumeration for CVE-2025-4969

GitHub Security Advisory for CVE-2025-4969

GHSA-ff3g-4fq3-jf4p · Severity: medium — A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly...

OS Trackers for CVE-2025-4969

vendor priority summary link
debian not yet assigned CVE-2025-4969 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-4969
redhat medium — https://access.redhat.com/security/cve/CVE-2025-4969
suse medium CVE-2025-4969 severity moderate: SUSE including 51 source package names (curl-8.14.1-slfo.1.1_4.1, latest:curl-8.14.1-slfo.1.1_4.1, …), 210 product×package rows across 49 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (49 product lines)): Fixed 210. https://www.suse.com/security/cve/CVE-2025-4969/
ubuntu medium CVE-2025-4969 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-4969

Affected software / configurations for CVE-2025-4969

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-4969

cvelogic Threat Intelligence