Bug 2496576 (CVE-2026-59087) - CVE-2026-59087 gimp: Heap buffer overflow in `file-seattle-filmworks` load — `fread` writes attacker-controlled length into undersized allocation
Summary: CVE-2026-59087 gimp: Heap buffer overflow in `file-seattle-filmworks` load — ...
Keywords:
Status: NEW
Alias: CVE-2026-59087
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2513088
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-02 15:16 UTC by OSIDB Bzimport
Modified: 2026-08-10 10:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-02 15:16:12 UTC 
The Seattle Filmworks file loader reads two file-position-derived values, index and metadata_len[1], uses only metadata_len[1] to size the allocation for photo_date, then freads index - metadata_len[1] bytes into it. Both values are attacker-controlled and independent. When index ≫ metadata_len[1], the read overflows the heap by up to several KB of attacker-controlled bytes.
In a build with _FORTIFY_SOURCE (Ubuntu default), glibc detects this at runtime and aborts. In a non-FORTIFY build the corruption is silent.

Issue Link: https://gitlab.gnome.org/GNOME/gimp/-/work_items/16491
Note You need to log in before you can comment on or make changes to this bug.