dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2026-5201

HIGH · 7.5 CVSS v3.1 Published 2026-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 flaw was found in the gdk-pixbuf library. This heap-based buffer overflow vulnerability occurs in the JPEG image loader due to improper validation of color component counts when processing a specially crafted JPEG image. A remote attacker can exploit this flaw without user interaction, for example, via thumbnail generation. Successful exploitation leads to application crashes and denial of service (DoS) conditions.

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

A heap-based buffer overflow vulnerability exists in the gdk-pixbuf library's JPEG image loader. The flaw stems from improper validation of color component counts when processing JPEG images, allowing a remote attacker to trigger the overflow via a specially crafted JPEG file without any user interaction, such as through automated thumbnail generation.

MitigationUpdate gdk-pixbuf to the patched version provided by your distribution or vendor. Prioritize updates on systems that automatically process untrusted images, such as file browsers, image viewers, and thumbnail generation services.

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
Enterprise LinuxOperating system
Affected:= 7.0= 8.0= 9.0= 10.0
Enterprise Linux Server AusOperating system
Affected:= 8.2= 8.4
Enterprise Linux Server TusOperating system
Affected:= 8.8
Gdk PixbufApplication
Affected:all versions

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Verify gdk-pixbuf is installed
    Run 'rpm -qa | grep gdk-pixbuf' (RHEL) or 'dpkg -l | grep gdk-pixbuf' (Debian-based) to list installed gdk-pixbuf packages
    Affected if gdk-pixbuf is present on the system regardless of version, as all versions are affected per the advisory
  2. Check the installed gdk-pixbuf version
    Run 'rpm -q --qf '%{VERSION}-%{RELEASE} ' gdk-pixbuf' or check the package details to identify the exact version installed
    Affected if The version matches any of the affected RHEL versions (7.0, 8.0, 9.0, 10.0, 8.2, 8.4, 8.8) or is any version of the Gnome Gdk Pixbuf library
  3. Confirm JPEG loader module is present
    Check for the JPEG image loader module in the gdk-pixbuf loaders directory, typically found at /usr/lib*/gdk-pixbuf-2.0/*/loaders/libpixbufloader-jpeg.so or /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
    Affected if The JPEG loader module exists on the system, indicating JPEG support is enabled in gdk-pixbuf
  4. Verify thumbnail generation services are active
    Check for running thumbnailer processes or examine thumbnail cache directories (e.g., ~/.cache/thumbnails, /var/cache/thumbnails) for recent activity. On GNOME systems, check if 'gvfsd-thumbnailer' or 'thumbnailers' services are running using 'systemctl list-units --type=service | grep -i thumbnail'
    Affected if Automatic thumbnail generation services are enabled or active, as the vulnerability can be triggered without user interaction during thumbnail creation

If gdk-pixbuf with JPEG support is installed and automatic thumbnail generation is enabled, the system is potentially vulnerable to CVE-2026-5201 through specially crafted JPEG images.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update gdk-pixbuf to the patched version provided by your distribution or vendor. Prioritize updates on systems that automatically process untrusted images, such as file browsers, image viewers, and thumbnail generation services.

Recommended fix Moderate confidence

Latest available gdk-pixbuf package via Red Hat Enterprise Linux update channels (refer to RHSA for specific version numbers)

  1. Update the system package cache: sudo dnf check-update or sudo yum check-update
  2. Apply the gdk-pixbuf security update: sudo dnf update gdk-pixbuf or sudo yum update gdk-pixbuf
  3. Restart any running applications that use gdk-pixbuf to ensure the updated library is loaded
  4. Verify the update was applied successfully: rpm -q gdk-pixbuf and check the installed version against Red Hat Security Advisories (RHSA)
Caveat Standard package update; minimal risk of breaking changes for this library update unless application-specific compatibility issues exist

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

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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