Bug 2497435 (CVE-2026-58388)

Summary:	CVE-2026-58388 gimp: gimp: Stack-based out-of-bounds write in Seattle FilmWorks loader
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	rhel-process-autobot, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in GIMP's Seattle FilmWorks (SFW94A) loader. A stack-based out-of-bounds write occurs in load_image() because a stack buffer sized as file_size - 0xE0 is later indexed using bounds based on file_size. This can corrupt stack memory and potentially lead to denial of service or arbitrary code execution.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-07-06 19:00:25 UTC

Stack-based out-of-bounds write in GIMP's Seattle FilmWorks (SFW94A) loader. In load_image() in file-seattle-filmworks.c, a stack VLA sized as file_size - 0xE0 is allocated, but subsequent bounds checks continue to use file_size. A crafted SFW file can therefore drive the JPEG marker search and repair logic past the VLA boundary and corrupt stack memory.

- Function: load_image()
- File: plug-ins/common/file-seattle-filmworks.c:261-428
- Fix: https://gitlab.gnome.org/GNOME/gimp/-/commit/c1263f39
- Upstream issue: https://gitlab.gnome.org/GNOME/gimp/-/issues/16231
- Acknowledgment: bb1abu