CVE-2026-5201: Gdk-pixbuf: gdk-pixbuf: denial of service via heap-based buffer overflow when processing a specially crafted jpeg image
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-5201 is a high-severity denial-of-service flaw in gdk-pixbuf2, an image-loading library. A specially crafted JPEG can crash applications that process it, including automatic thumbnail generation paths. The sources describe availability impact, not data theft or privilege escalation.
Executive priority
Prioritize patching in normal high-severity windows, faster for externally facing upload or content-processing services. The business risk is service disruption from crafted images, not confirmed data compromise. No source indicates active exploitation, but the no-interaction attack path increases urgency.
Technical view
The flaw is a heap-based buffer overflow in the gdk-pixbuf JPEG loader caused by improper validation of color component counts. Red Hat rates it high with CVSS 3.1 score 7.5: network exploitable, low complexity, no privileges, no user interaction, availability impact only.
Likely exposure
Exposure is most likely on affected Red Hat Enterprise Linux systems with gdk-pixbuf2 installed that process untrusted JPEG files, especially automated preview, thumbnail, indexing, or image-handling workflows. Listed affected streams include RHEL 7 ELS, RHEL 8 variants, RHEL 9 variants, and RHEL 10.
Exploitation context
The source bundle says remote exploitation can occur without user interaction, for example through thumbnail generation. CISA KEV status is false, and no provided source states active exploitation. Treat exploitability as plausible for exposed image-processing paths, but do not assume exploitation in the wild from this evidence alone.
Researcher notes
Focus validation on package presence, RHEL stream, and whether gdk-pixbuf2 handles attacker-controlled JPEGs. The affected-package list is Red Hat-specific. The bundle does not establish upstream non-Red Hat affected versions, proof-of-concept availability, or memory-corruption impact beyond denial of service.
Mitigation direction
Apply the relevant Red Hat security advisory updates for each affected RHEL stream.
Prioritize systems that automatically process externally supplied JPEG images.
Reduce or isolate automated thumbnailing of untrusted uploads until patched.
Check vendor guidance before applying compensating controls not named in advisories.
Validation and detection
Inventory installed gdk-pixbuf2 package versions across affected RHEL systems.
Map applications and services that process JPEGs through gdk-pixbuf2.
Confirm applicable RHSA updates are installed for each RHEL lifecycle stream.
Review crash logs for image-processing failures around untrusted JPEG handling.
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-122: 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.
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-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.