CVE-2025-13601
Gnome Glib integer overflow
- Published26 Nov 2025
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:0936
- https://access.redhat.com/errata/RHSA-2026:0975
- https://access.redhat.com/errata/RHSA-2026:0991
- https://access.redhat.com/errata/RHSA-2026:1323
- https://access.redhat.com/errata/RHSA-2026:1324
- https://access.redhat.com/errata/RHSA-2026:1326
- https://access.redhat.com/errata/RHSA-2026:1327
- https://access.redhat.com/errata/RHSA-2026:1465
- https://access.redhat.com/errata/RHSA-2026:1608
- https://access.redhat.com/errata/RHSA-2026:1624
and 23 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-13601 being actively exploited?
CVE-2025-13601 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.32%.
How severe is CVE-2025-13601?
CVE-2025-13601 has a CVSS 3.1 base score of 7.7, rated high. EPSS estimates a 0.32% probability of exploitation.
Which products are affected by CVE-2025-13601?
Affected products include Gnome Glib, Redhat Ceph Storage, Redhat Codeready Linux Builder, Redhat Codeready Linux Builder For Arm64, Redhat Codeready Linux Builder For Arm64 Eus, and 19 more.
How do I fix CVE-2025-13601?
Upgrade affected software to a fixed version, for example Gnome Glib 2.86.3 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-13601 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.