dbcve.org
Use After FreeWeakness · CWE-416

CVE-2025-12105

HIGH · 7.5 CVSS v3.1 Published 2025-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A use-after-free vulnerability exists in libsoup's asynchronous message queue handling for 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 between queue operations, leading to memory corruption and application crashes via denial-of-service.

MitigationApply vendor patches for libsoup when released; until then, restrict or monitor HTTP/2 connections from untrusted sources to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify libsoup installation and version
    Run 'pkg-config --modversion libsoup-3.0' or 'pkg-config --modversion libsoup-2.4' to determine the installed libsoup version. For systems without pkg-config, check package manager output (apt list --installed | grep libsoup, rpm -qa | grep libsoup, etc.)
    Affected if The installed libsoup version falls within any affected version range and the application uses HTTP/2 connections
  2. Confirm HTTP/2 support is enabled
    Inspect the application's libsoup configuration or client creation code. Look for SoupSession or SoupClient usage where HTTP/2 is explicitly enabled via SoupHTTPVersion (e.g., SOUP_HTTP_2_0) or via configuration options. Check configuration files for enable-http2=true or similar settings.
    Affected if HTTP/2 support is enabled in the libsoup configuration being used by the application
  3. Identify applications using libsoup for network operations
    Review application dependencies to confirm linkage with libsoup. For web servers or proxies using libsoup (such as GNOME's gwiberd or custom applications), examine running processes and their runtime behavior. Use 'ldd <binary>' to check for libsoup linkage.
    Affected if An application linked against libsoup is handling HTTP/2 network traffic that could be aborted
  4. Monitor for crash patterns consistent with double-free
    Review system crash logs, application logs, and core dumps for patterns indicating memory corruption or double-free errors in libsoup network handling code. Look for log entries mentioning 'libsoup', 'HTTP/2', 'queue', or memory corruption errors occurring during network abort scenarios.
    Affected if Crash logs or memory dumps show use-after-free or double-free behavior in libsoup's message queue handling during network operations

A user is affected if their system has a vulnerable libsoup version with HTTP/2 support enabled and applications handling HTTP/2 connections that could experience network abort conditions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for libsoup when released; until then, restrict or monitor HTTP/2 connections from untrusted sources to reduce attack surface.

Recommended fix Moderate confidence

Upgrade libsoup to the version containing the CVE-2025-12105 fix; check Red Hat or GNOME project security advisories for the specific fixed version number

  1. Check your distribution's package manager for available libsoup updates (e.g., apt update && apt-cache policy libsoup2.4-1 on Debian/Ubuntu, dnf check-update on Fedora/RHEL, or pacman -Sy on Arch)
  2. Upgrade libsoup to the latest available version in your distribution's repositories
  3. Restart any GNOME or WebKit-based applications (such as epiphany, geary, or WebKitGTK applications) to ensure they load the updated library
  4. Verify the fix by checking the libsoup version matches the patched release (consult your vendor's security advisory for the exact version number)
Caveat Minor: Upgrading libsoup should not introduce breaking changes for typical applications, but always test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12105 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data