CVE-2025-6052

CWE-190Integer Overflow9 documents9 sources
Severity
7.5HIGH
EPSS
0.3%
top 46.60%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
Timeline
PublishedJun 13
Latest updateJan 15

Description

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.

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitability: 2.2 | Impact: 1.4

Affected Packages2 packages

Debianglib2.0< 2.84.3-1+1
NVDgnome/glib2.75.32.84.3

🔴Vulnerability Details

3
GHSA
GHSA-99rj-3595-5frj: A flaw was found in how GLib’s GString manages memory when adding data to strings2025-06-13
CVEList
Glib: integer overflow in g_string_maybe_expand() leading to potential buffer overflow in glib gstring2025-06-13
OSV
CVE-2025-6052: A flaw was found in how GLib’s GString manages memory when adding data to strings2025-06-13

📋Vendor Advisories

5
Oracle
Oracle Oracle Java SE Risk Matrix: JavaFX (glibc) — CVE-2025-60522026-01-15
Ubuntu
GLib vulnerabilities2026-01-06
Red Hat
glib: Integer overflow in g_string_maybe_expand() leading to potential buffer overflow in GLib GString2025-06-13
Microsoft
Glib: integer overflow in g_string_maybe_expand() leading to potential buffer overflow in glib gstring2025-06-10
Debian
CVE-2025-6052: glib2.0 - A flaw was found in how GLib’s GString manages memory when adding data to string...2025
CVE-2025-6052 (HIGH CVSS 7.5) | A flaw was found in how GLib’s GStr | cvebase.io