CVE-2025-46420 | Libsoup: memory leak on soup_header_parse_quality_list() via soup-headers.c

A flaw was found in libsoup. It is vulnerable to memory leaks in the soup_header_parse_quality_list() function when parsing a quality list that contains elements with all zeroes.

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

CVE-2025-46420 is rated Low Risk (38.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.47%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-46420

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-06-15 0.57% 0.47% -0.10%
2 2026-06-12 0.47% 0.57% +0.09%
3 2026-06-02 — 0.47% —

Full EPSS history (13 records total)

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

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:R/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:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2025-46420

OS Trackers for CVE-2025-46420

vendor priority summary link
debian not yet assigned CVE-2025-46420 not yet assigned priority: Debian including 2 source packages (libsoup2.4, libsoup3), 7 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 2. https://security-tracker.debian.org/tracker/CVE-2025-46420
redhat medium — https://access.redhat.com/security/cve/CVE-2025-46420
suse medium CVE-2025-46420 severity moderate: SUSE including 57 source package names (2.2.1-7.31:libvmtools0-13.0.5-160000.1.1, 2.2.1-7.31:open-vm-tools-13.0.5-160000.1.1, …), 259 product×package rows across 51 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (51 product lines)): Fixed 259. https://www.suse.com/security/cve/CVE-2025-46420/
ubuntu medium CVE-2025-46420 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, not-affected 3, DNE 1, needed 1. https://ubuntu.com/security/CVE-2025-46420

Affected software / configurations for CVE-2025-46420

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-46420

cvelogic Threat Intelligence