dbcve.org
GlibApplication · Gnome

CVE-2025-6052

HIGH · 7.5 CVSS v3.1 Published 2025-06-13
Fix available
A fix is available. Upgrade to after 2.84.3 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 how GLib’s GString manages memory when adding data to strings. If a string is already very large, combining it with more input can cause a hidden overflow in the size calculation. This makes the system think it has enough memory when it doesn’t. As a result, data may be written past the end of the allocated memory, leading to crashes or memory corruption.

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 · high confidence

GLib's GString contains an integer overflow vulnerability in size calculations when appending data to already-large strings. This causes the allocator to allocate insufficient memory, resulting in a heap buffer overflow when data is written past the end of the allocated buffer, leading to potential crashes or memory corruption.

MitigationUpdate GLib to the latest version containing the fix. As a temporary workaround, limit the maximum size of strings processed by GString operations or validate string lengths before concatenation.

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.75.3, <= 2.84.3

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. Determine installed GLib version
    Run `pkg-config --modversion glib-2.0` or check your system package manager (dpkg -l libglib2.0-0, rpm -q glib2, etc.)
    Affected if The version returned is 2.75.3, 2.76.x, 2.77.x, 2.78.x, 2.79.x, 2.80.x, 2.81.x, 2.82.x, 2.83.x, or 2.84.3 (any version from 2.75.3 through 2.84.3 inclusive)
  2. Confirm GString usage in your application
    Search your source code for GString function calls such as g_string_new, g_string_append, g_string_append_printf, g_string_insert, g_string_truncate, or similar GString API functions
    Affected if Your code or any linked library uses GString operations to build or modify strings
  3. Identify large string handling patterns
    Review code paths that append data to GString objects with potentially large or unbounded input, especially where input size is not validated before concatenation
    Affected if Your application constructs large strings via GString append operations without limiting maximum string size
  4. Check for untrusted input in string operations
    Examine whether user-supplied or network-supplied data flows into GString append, printf-style, or insert functions without length validation
    Affected if Untrusted or externally-controlled data is passed to GString manipulation functions

You are affected if your installed GLib version falls between 2.75.3 and 2.84.3 inclusive AND your application uses GString operations to handle large strings, particularly with unvalidated or user-controlled input lengths.

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 a release after 2.84.3
Interim mitigation

Update GLib to the latest version containing the fix. As a temporary workaround, limit the maximum size of strings processed by GString operations or validate string lengths before concatenation.

Recommended fix Moderate confidence

GLib 2.84.4 or later (or 2.85.x/2.86.x stable release)

  1. 1. Identify the current installed GLib version using 'pkg-config --modversion glib-2.0' or 'glib-config --version'
  2. 2. Check your system's package manager for available GLib updates (e.g., 'apt list --upgradable', 'yum check-update', 'dnf check-update')
  3. 3. Update GLib to version 2.84.4 or later using your system's package manager (e.g., 'sudo apt update && sudo apt upgrade libglib2.0-dev' or 'sudo dnf update glib2')
  4. 4. Verify the updated version meets the fix requirement: run 'pkg-config --modversion glib-2.0' and confirm version > 2.84.3
  5. 5. Rebuild any dependent applications that statically link against GLib after the upgrade
  6. 6. Test critical functionality to ensure compatibility with the updated library
Caveat Major GLib updates may introduce API/ABI changes; review release notes for breaking changes and test applications against the new version before production deployment

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

Fix this in Glib Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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