dbcve.org
Codeready Linux BuilderApplication · Redhat

CVE-2025-13601

HIGH · 7.7 CVSS v3.1 Published 2025-11-26
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
82/100
Remediation priority · High
Public exploit No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-190

An arithmetic operation produces a value too large for its type and wraps around to an unexpected — often tiny or negative — number. That miscalculated value then drives a memory allocation or a bounds check, opening the door to corruption. The fix is checked arithmetic and validating sizes before they're used.

General guidance for the integer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Codeready Linux BuilderApplication
Affected:= 9.0
Codeready Linux Builder For Ibm Z SystemsApplication
Affected:= 9.0_s390x= 10.0_s390x= 8.0_s390x= 9.4_s390x= 9.6_s390x
Codeready Linux Builder For Power Little EndianApplication
Affected:= 9.0_ppc64le= 10.0_ppc64le= 8.0_ppc64le= 9.4_ppc64le= 9.6_ppc64le
Codeready Linux Builder For X86 64Application
Affected:= 9.0= 10.0= 8.0= 9.4= 9.6
Enterprise Linux For Arm 64Operating system
Affected:= 9.0= 10.0= 8.0= 9.2= 9.4= 9.6
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 9.0_s390x= 10.0_s390x= 8.0_s390x= 9.2_s390x= 9.4_s390x= 9.6_s390x
Enterprise Linux For Power Little EndianOperating system
Affected:= 9.0_ppc64le= 10.0_ppc64le= 8.0_ppc64le= 9.2_ppc64le= 9.4_ppc64le= 9.6_ppc64le
Enterprise Linux For X86 64Operating system
Affected:= 9.0= 10.0= 8.0= 9.2= 9.4= 9.6= 8.6= 8.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Recommended fix Moderate confidence

Update to the glib2 package version specified in the Red Hat Security Advisory (RHSA) for this CVE - the advisory is published on access.redhat.com for the affected RHEL versions (8.0, 9.0, 9.2, 9.4, 10.0)

  1. Run 'dnf check-update' or 'yum check-update' to check for available glib updates
  2. Apply the security update using 'dnf update glib2' or 'yum update glib2'
  3. Reboot the system if the glib library requires it to ensure the updated library is loaded
  4. Verify the fix by checking the installed glib version matches the patched release (e.g., run 'rpm -q glib2' and compare to the RHSA advisory)
Caveat Standard glib library updates rarely cause application breakage; however, rebuild of dependent packages may be needed in rare cases

Generated from the published advisory — verify against the referenced sources before acting.

No vendor fix exists Codeready Linux Builder has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $3,200. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13601 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13601 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data