# CVE-2025-12105: Libsoup: heap use-after-free in libsoup message queue handling during http/2 read completion > Remote attackers can cause denial of service in applications using libsoup by triggering specific HTTP/2 read and cancel sequences that lead to a use-after-free crash. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Oct 2025 - **Updated:** 29 Jun 2026 - **Also known as:** ALSA-2025:23139, AZL-72841, DEBIAN-CVE-2025-12105, ECHO-4ebf-bc2c-395e, GHSA-gppq-jw9r-4v4j, RHSA-2025:23139, RHSA-2025:23437, RLSA-2025:23139, SUSE-SU-2026:0017-1, UBUNTU-CVE-2025-12105, USN-7932-1, openSUSE-SU-2025:15766-1 ## What is CVE-2025-12105? CVE-2025-12105 is a high-severity use after free vulnerability in GNOME Red Hat Enterprise Linux 10, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2025-12105? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libsoup3-doc` | AlmaLinux:10 | All versions | 3.6.5-3.el10_1.7 | | `libsoup3` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.7 | | `libsoup3-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.7 | | `libsoup3-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.7 | | `libsoup3-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.7 | | `libsoup3-doc` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.6.5-3.el10_1.7 | | `libsoup3` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.10 | | `libsoup3-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.10 | | `libsoup3-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.10 | | `libsoup3-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.10 | | `libsoup3-doc` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.10 | | `libsoup3` | Rocky Linux:10 | All versions | 0:3.6.5-3.el10_1.7 | | `libsoup` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 3.4.4-150600.3.21.1 | | `libsoup` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 3.4.4-150600.3.21.1 | | `libsoup` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 3.4.4-150600.3.21.1 | | `libsoup` | openSUSE:Leap 15.6 | All versions | 3.4.4-150600.3.21.1 | | `libsoup` | openSUSE:Tumbleweed | All versions | 3.6.5-9.1 | ## How do I fix CVE-2025-12105? Apply the vendor's patch. ## Is CVE-2025-12105 being exploited? There is no known exploitation of CVE-2025-12105 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-12105 and fix it if it is affected. What it is: CVE-2025-12105 is a high-severity use after free vulnerability in GNOME Red Hat Enterprise Linux 10, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-12105 in the wild and no public exploit code. Affected product: GNOME Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-12105/ (Markdown: https://insights.sbomify.com/CVE-2025-12105/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12105 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12105 - OSV: https://osv.dev/vulnerability/CVE-2025-12105 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-12105/ Summaries are generated and may contain mistakes; the official description above is the record.