Glib: integer overflow in g_string_maybe_expand() leading to potential buffer overflow in glib gstring
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-6052US | high7.5 | — | ||
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 th… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/CVE-2025-6052ADVISORY
- https://bugzilla.redhat.com/show_bug.cgi?id=2372666ADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2025-6052WEB
- https://openjdk.org/groups/vulnerability/advisories/2026-01-20WEB
- https://www.oracle.com/security-alerts/cpuapr2026.htmlWEB
- https://www.oracle.com/security-alerts/cpujan2026.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan