CVE-2026-58013: Buffer Over-read in GNOME GLib
A flaw was found in GLib. A buffer over-read can occur in g_io_channel_read_line_backend() in the giochannel.c file when a custom line terminator with a length greater than one is set, causing memcmp to read past the GString buffer. This vulnerability can cause a minor information disclosure of 7 bytes or a denial of service when the buffer over-read crosses a page boundary.
AI Analysis
Technical Summary
CVE-2026-58013 is a buffer over-read vulnerability in the GLib library, specifically in the g_io_channel_read_line_backend() function within giochannel.c. When a custom line terminator string longer than one byte is set using g_io_channel_set_line_term(), the memcmp operation in g_io_channel_read_line_backend() may read beyond the allocated GString buffer. This can result in an information disclosure of up to 7 bytes or a denial of service due to application crash if the over-read crosses an unmapped memory page boundary. The vulnerability has a CVSS 3.1 base score of 6.5 (medium severity) with network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, low confidentiality impact, no integrity impact, and low availability impact. Red Hat's advisory confirms the issue and recommends restricting custom line terminators to a maximum length of one byte or using default terminators to neutralize the vulnerability. No official patch version is explicitly stated in the provided data, but Red Hat has issued security updates including this fix in mingw-glib2 packages for Red Hat Enterprise Linux 8.
Potential Impact
Exploitation of this vulnerability can lead to minor information disclosure of 7 bytes from out-of-bounds memory or cause a denial of service via application crash when the buffer over-read crosses a page boundary. The information disclosure may aid attackers in bypassing protection mechanisms such as ASLR. The denial of service impact is considered low as crashes are reliably reproducible in AddressSanitizer builds but not commonly in production environments.
Mitigation Recommendations
To mitigate this vulnerability, applications should restrict any custom line terminator string passed to g_io_channel_set_line_term() to a maximum length of one byte before calling g_io_channel_read_line_backend(). Using the default line terminators completely neutralizes the issue. Additionally, Red Hat has released security updates for affected packages (e.g., mingw-glib2 for RHEL 8) that address this vulnerability. Applying these official updates is recommended where applicable. Patch status is confirmed via Red Hat advisory; users should consult vendor advisories for update availability and instructions.
CVE-2026-58013: Buffer Over-read in GNOME GLib
Description
A flaw was found in GLib. A buffer over-read can occur in g_io_channel_read_line_backend() in the giochannel.c file when a custom line terminator with a length greater than one is set, causing memcmp to read past the GString buffer. This vulnerability can cause a minor information disclosure of 7 bytes or a denial of service when the buffer over-read crosses a page boundary.
CVSS v3.1
Score 6.5medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-58013 is a buffer over-read vulnerability in the GLib library, specifically in the g_io_channel_read_line_backend() function within giochannel.c. When a custom line terminator string longer than one byte is set using g_io_channel_set_line_term(), the memcmp operation in g_io_channel_read_line_backend() may read beyond the allocated GString buffer. This can result in an information disclosure of up to 7 bytes or a denial of service due to application crash if the over-read crosses an unmapped memory page boundary. The vulnerability has a CVSS 3.1 base score of 6.5 (medium severity) with network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, low confidentiality impact, no integrity impact, and low availability impact. Red Hat's advisory confirms the issue and recommends restricting custom line terminators to a maximum length of one byte or using default terminators to neutralize the vulnerability. No official patch version is explicitly stated in the provided data, but Red Hat has issued security updates including this fix in mingw-glib2 packages for Red Hat Enterprise Linux 8.
Potential Impact
Exploitation of this vulnerability can lead to minor information disclosure of 7 bytes from out-of-bounds memory or cause a denial of service via application crash when the buffer over-read crosses a page boundary. The information disclosure may aid attackers in bypassing protection mechanisms such as ASLR. The denial of service impact is considered low as crashes are reliably reproducible in AddressSanitizer builds but not commonly in production environments.
Mitigation Recommendations
To mitigate this vulnerability, applications should restrict any custom line terminator string passed to g_io_channel_set_line_term() to a maximum length of one byte before calling g_io_channel_read_line_backend(). Using the default line terminators completely neutralizes the issue. Additionally, Red Hat has released security updates for affected packages (e.g., mingw-glib2 for RHEL 8) that address this vulnerability. Applying these official updates is recommended where applicable. Patch status is confirmed via Red Hat advisory; users should consult vendor advisories for update availability and instructions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-06-26T20:59:47.855Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-58013","vendor":"Red Hat"}]
Threat ID: 6a43c34927e9c79719d5bd60
Added to database: 06/30/2026, 13:23:21 UTC
Last enriched: 08/03/2026, 19:48:14 UTC
Last updated: 08/10/2026, 12:41:12 UTC
Views: 122
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.