CVE-2025-12105 | Libsoup: heap use-after-free in libsoup message queue handling during http/2 read completion

A flaw was found in the asynchronous message queue handling of the libsoup library, widely used by GNOME and WebKit-based applications to manage HTTP/2 communications. When network operations are aborted at specific timing intervals, an internal message queue item may be freed twice due to missing state synchronization. This leads to a use-after-free memory access, potentially crashing the affected application. Attackers could exploit this behavior remotely by triggering specific HTTP/2 read and cancel sequences, resulting in a denial-of-service condition.

Published: 2025-10-23 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-12105 is rated Low Risk (37.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.07%). Mandatory action: 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-12105

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-04-02 0.05% 0.07% +0.02%
2 2026-03-21 0.05% 0.05% -0.00%
3 2025-10-29 0.05%

Full EPSS history (4 records total)

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

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

OS Trackers for CVE-2025-12105

vendor priority summary link
debian unimportant CVE-2025-12105 unimportant 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-12105
redhat medium https://access.redhat.com/security/cve/CVE-2025-12105
suse high CVE-2025-12105 severity important: SUSE including 37 source package names (latest:libpython3_11-1_0-3.11.13-1.1, latest:python311-base-3.11.13-1.1, …), 255 product×package rows across 51 product lines (Container suse/sl-micro/6.0/toolbox, Image SLE-Micro, … (51 product lines)): Known Not Affected 138, Fixed 113, First Fixed 4. https://www.suse.com/security/cve/CVE-2025-12105/
ubuntu medium CVE-2025-12105 medium priority: Ubuntu including 2 source packages (libsoup2.4, libsoup3), 13 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): not-affected 7, released 4, needed 2. https://ubuntu.com/security/CVE-2025-12105

Affected software / configurations for CVE-2025-12105

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-12105

cvelogic Threat Intelligence