dbcve.org
OpenshiftApplication · Redhat

CVE-2025-14512

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 2.86.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 flaw was found in glib. This vulnerability allows a heap buffer overflow and denial-of-service (DoS) via an integer overflow in GLib's GIO (GLib Input/Output) escape_byte_string() function when processing malicious file or remote filesystem attribute values.

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 · high confidence

Heap buffer overflow and DoS vulnerability in GLib's GIO escape_byte_string() function due to an integer overflow when processing malicious file or remote filesystem attribute values. The overflow allows attackers to corrupt heap memory via crafted attribute values.

MitigationUpdate GLib to the patched version that fixes the integer overflow in escape_byte_string(). For systems where immediate patching is not possible, consider input validation on filesystem attribute values before passing to GLib functions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
OpenshiftApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 7.0= 8.0= 9.0= 10.0
GlibApplication
Affected:< 2.86.3

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GLib version
    Run 'pkg-config --modversion glib-2.0' or 'rpm -q glib2' on RHEL systems to determine the installed GLib version
    Affected if version is lower than 2.86.3
  2. Check if GIO module is present
    Verify the glib2 package includes GIO by checking for gio-unix-2.0.so or gio module files in /usr/lib/ or /usr/lib64/
    Affected if GIO module files exist and GLib version is below 2.86.3
  3. Identify applications using GIO file system functions
    Review application dependencies or audit code for usage of g_file_attribute_* functions, particularly g_file_attribute_value_pack() or escape_byte_string() related code paths
    Affected if applications process file or remote filesystem attribute values from untrusted sources using GIO functions
  4. Check for extended attribute handling in applications
    Audit custom file handling services or remote filesystem clients that process extended attributes via GLib GIO APIs
    Affected if extended attributes from external or remote sources are processed through GLib's GIO functions without prior validation

A system is affected if it runs GLib version lower than 2.86.3 and has applications or services that use GIO functions to process file or remote filesystem attribute values from potentially untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Upgrade available Upgrade to 2.86.3 or later
Fixed in 2.86.3
Interim mitigation

Update GLib to the patched version that fixes the integer overflow in escape_byte_string(). For systems where immediate patching is not possible, consider input validation on filesystem attribute values before passing to GLib functions.

Recommended fix Moderate confidence

Glib 2.86.3 or later; For RHEL apply latest vendor glib2 errata; For OpenShift 4.0 apply corresponding RHSA

  1. Check current glib version: rpm -qa | grep glib2 or pkg-config --modversion glib-2.0
  2. For RHEL systems: run 'dnf check-update' or 'yum check-update' to see available glib updates
  3. Apply vendor security updates: sudo dnf update glib2 or sudo yum update glib2 (this will install glib >= 2.86.3 or vendor-patched version)
  4. For OpenShift 4.0: Apply Red Hat security advisory RHSA-XXXX:XXXX for glib (obtain from access.redhat.com) using 'oc adm upgrade' or cluster version operator
  5. Reboot or restart affected services to load updated glib libraries
  6. Verify fix: rpm -qa | grep glib2 and confirm version >= 2.86.3
Caveat Upgrading glib libraries may require restarting applications that link against glib; test in staging environment first

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

Fix this in Openshift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14512 — 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-14512 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