dbcve.org
GlibApplication · Gnome

CVE-2025-4056

HIGH · 7.5 CVSS v3.1 Published 2025-07-28
Fix available
A fix is available. Upgrade to 2.84.1 or later.
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 GLib. A denial of service on Windows platforms may occur if an application attempts to spawn a program using long command lines.

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

GLib's program spawning functionality on Windows does not properly handle long command lines, leading to a denial of service when applications attempt to spawn programs with excessively long arguments.

MitigationLimit command line lengths used when spawning programs on Windows, and apply any available GLib updates/patches that address this handling issue.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GlibApplication
Affected:< 2.84.1

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. Confirm Windows platform
    Verify the operating system is Windows. This vulnerability only affects GLib on Windows platforms. Check system properties or run 'systeminfo' on Windows or 'uname -a' on Unix-like systems to identify the OS.
    Affected if The system is NOT running Windows - the vulnerability does not apply to non-Windows platforms.
  2. Identify GLib installation
    Locate the GLib library on the system. On Windows, check for glib.dll in system directories (e.g., C:\Windows\System32, or application-specific paths). Use 'where glib.dll' or examine the application's dependencies with tools like Dependencies Walker or dumpbin.
    Affected if GLib is not installed on the system - the vulnerability does not apply.
  3. Determine GLib version
    Check the version of the installed GLib DLL. Right-click glib.dll, select Properties, then Details to view File Version. Alternatively, use a tool like exiftool or examine the version resource embedded in the DLL.
    Affected if The installed GLib version is 2.84.1 or higher - the version is not affected by this CVE.
  4. Verify application uses program spawning
    Identify if any applications on the system use GLib's program spawning functions (g_spawn* functions such as g_spawn_command_line_sync, g_spawn_async, g_spawn_sync, g_spawn_command_line_async). Review application source code if available, or monitor process behavior during execution.
    Affected if No applications use GLib's spawning functions - the denial of service condition cannot be triggered through this attack surface.

A user is affected if they are running Windows with GLib version lower than 2.84.1 AND have applications that use GLib's program spawning functionality with long command line arguments.

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
Upgrade available Upgrade to 2.84.1 or later
Fixed in 2.84.1
Interim mitigation

Limit command line lengths used when spawning programs on Windows, and apply any available GLib updates/patches that address this handling issue.

Recommended fix Moderate confidence

Glib 2.84.1

  1. Identify the current Glib version installed on your system (e.g., run `pkg-config --modversion glib-2.0` or check your package manager)
  2. Update your system's package repository to ensure you have access to the latest packages
  3. Upgrade Glib to version 2.84.1 or later using your system's package manager (e.g., `apt update && apt install libglib2.0-dev` on Debian/Ubuntu, `dnf update glib2` on Fedora/RHEL, or `yum update glib2` on CentOS)
  4. If building from source, download Glib 2.84.1 or later from the official GNOME GitLab repository and compile following the standard build process
  5. Verify the upgraded version matches or exceeds 2.84.1
  6. Rebuild any dependent applications if necessary to ensure compatibility with the new Glib version
Caveat Minimal risk - this appears to be a bugfix release addressing a DoS vulnerability; however, always test in a non-production environment first

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

Fix this in Glib Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4056 — 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-4056 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