Technical impact
FreeImage through version 3.18.0 and the danoli3 fork before 3.19.25 contain a heap buffer overflow in PluginGIF.cpp that allows an attacker to write past the canvas allocation using unclipped GIF frame rectangles. When a GIF file is loaded with GIF_PLAYBACK, an attacker can craft a frame whose left offset plus width exceeds the logical screen width, causing GifPlaybackCompositeFrame() and GifPlaybackFillRect() to corrupt heap memory. This out-of-bounds write can lead to program state corruption or arbitrary code execution (CWE-787).
Affected Systems
The flaw affects the FreeImage library maintained by the FreeImage Project and the danoli3 fork. All releases prior to 3.19.25 are impacted; an attacker must be able to supply a crafted GIF to an application that uses FreeImage's GIF_PLAYBACK mode.
Risk and Exploitability
The CVSS base score of 8.5 indicates a high severity flaw that could allow an attacker to execute arbitrary code by corrupting heap memory. The EPSS score of less than 1% suggests that exploitation of this vulnerability is currently uncommon. The vulnerability is not listed in the CISA KEV catalog. To exploit it, an attacker would need to supply a specially crafted GIF file to an application that processes images via the GIF_PLAYBACK mode. Such a file might be introduced locally through user‑provided data or, potentially, delivered remotely if the application accepts images from untrusted network sources. The remote nature of the attack vector is inferred from the need to present a GIF file, but no explicit statement confirms remote delivery, so the exact vector remains uncertain.