GEGL EUVD-2026-90475

Exploitation requires a local user to open an attacker-crafted Radiance HDR file whose header declares a width larger than the actual uncompressed scanline, in an application that uses GEGL's Radiance HDR loader (notably GIMP). The limiting factors are significant: the attack vector is local (AV:L), it depends on victim user interaction (UI:R - the file must be opened), and no authentication to GEGL itself is involved. There is no network-facing or default-service exposure; the impact is confined to crashing the consuming application (A:H, availability only).

All signals point to a low-priority, availability-only denial-of-service. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, 5.5 Medium) is self-consistent with the description: the attack is LOCAL and requires a user to open a crafted Radiance HDR file (UI:R), with no confidentiality or integrity impact - only an application crash. No EPSS score, KEV entry, or public POC was provided, so exploitation status is 'no public exploit identified at time of analysis.' There is no SSVC data in the input. The one notable data conflict is the input Tags: 'Information Disclosure' is contradicted by the CVSS vector's C:N (there is no data leak - an out-of-bounds READ that crashes the process, not one that exfiltrates memory to the attacker), and 'Buffer Overflow' is a loose label for what CWE-125 and the description make clear is an out-of-bounds read, not a write. Net: this is a genuine-but-low-severity crash bug, not an urgent RCE; priority should track ordinary distro patch cadence rather than emergency response.

An attacker crafts a malicious Radiance HDR (.hdr) image whose header declares a width larger than the actual uncompressed scanline data and distributes it (email attachment, download, embedded asset). When a victim opens the file in GIMP or any application linking GEGL's HDR loader, the loader reads past the end of the memory-mapped buffer and the application crashes. No public exploit code was identified, and the out-of-bounds read yields a denial of service only, not code execution or data disclosure.