CVE-2025-13601: Glib: integer overflow in in g_escape_uri_string()
A heap-based buffer overflow problem was found in glib through an incorrect calculation of buffer size in the g_escape_uri_string() function. If the string to escape contains a very large number of unacceptable characters (which would need escaping), the calculation of the length of the escaped string could overflow, leading to a potential write off the end of the newly allocated string.
Security readout for executives and security teams
Plain-English summary
CVE-2025-13601 is a memory corruption flaw in GLib, a common Linux system library. A specially large string needing URI escaping can cause an integer overflow and heap buffer overflow. Red Hat rates it high because successful exploitation could corrupt data or crash affected software. No source provided indicates active exploitation.
Executive priority
Treat as a high-priority platform library update, especially on multi-user Linux systems and shared application hosts. It is not currently supported by the provided sources as internet-exploited or actively exploited, so prioritize through normal emergency patch governance rather than incident response escalation.
Technical view
The flaw is in GLib's g_escape_uri_string(). Incorrect escaped-length calculation can overflow when input contains many unacceptable characters, causing writes past a newly allocated heap buffer. The CVSS v3.1 score is 7.7, with local attack vector, low complexity, no privileges, and high integrity and availability impact.
Likely exposure
Exposure is most relevant on listed Red Hat Enterprise Linux systems with affected glib2 or mingw-glib2 packages. Risk depends on whether local users or processes can drive applications into calling g_escape_uri_string() with extremely large attacker-controlled input.
Exploitation context
The provided CVSS vector is local, not network. The source bundle does not show CISA KEV listing or other evidence of active exploitation. Practical impact likely depends on the consuming application, input path, memory protections, and whether the overflow is reachable in normal workflows.
Researcher notes
Key unknowns are application reachability and exploitability beyond corruption or denial of service. The bug requires extremely large inputs with many escapable characters. Validate affected package versions from vendor advisories and avoid assuming exposure unless a local or application-mediated input path reaches g_escape_uri_string().
Mitigation direction
Apply the applicable Red Hat RHSA update for each affected RHEL stream.
Prioritize systems where untrusted local users or workloads can influence URI escaping inputs.
Track GLib package guidance from Red Hat or your Linux distribution vendor.
Include bundled or statically linked GLib copies in software inventory review.
Validation and detection
Inventory glib2 and mingw-glib2 package versions across affected RHEL versions.
Map each host to the relevant Red Hat advisory and package stream.
Confirm updated packages are installed after maintenance.
Review application inventories for software using GLib URI escaping paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.