Quick answers
- Is CVE-2026-92183 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92183 being exploited in the wild.
- How severe is CVE-2026-92183?
- High severity, with a CVSS score of 7.8, published 21 October 2026.
- Which products and versions are affected?
- GNOME GIMP.
- Is there a fix for CVE-2026-92183?
- A patch was published on 2026-09-16: GIMP issued an update; fix available at https://gitlab.gnome.org/GNOME/gimp/-/commit/175e28961a4679be8762a2d4d5a297faa82aebd9 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92183 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-92183?
- Check whether you run Gnome GIMP. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in GIMP's APNG file parsing code due to insufficient validation of user-supplied data length before copying to a stack buffer. The attack requires user interaction (opening a malicious APNG file) and runs in the context of the GIMP process. An attacker can craft a malicious APNG file to trigger the overflow and achieve arbitrary code execution.
Affected products
- GNOME GIMP
Timeline
- 2026-04-29: disclosed: Vulnerability reported to vendor
- 2026-09-16: advisory: Coordinated public release of advisory
- 2026-09-16: patched: GIMP issued an update; fix available at https://gitlab.gnome.org/GNOME/gimp/-/commit/175e28961a4679be8762a2d4d5a297faa82aebd9