Quick answers
- Is CVE-2026-58381 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58381 being exploited in the wild.
- How severe is CVE-2026-58381?
- Medium severity, with a CVSS score of 6.1, published 2 July 2026.
- Which products and versions are affected?
- GNOME GIMP 3.2.1; Red Hat Red Hat Enterprise Linux 7 affected; Red Hat Red Hat Enterprise Linux 8 affected; Red Hat Red Hat Enterprise Linux 9 affected.
- Is there a fix for CVE-2026-58381?
- A patch was published on 2026-07-02: Upstream fix committed to GNOME GitLab repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58381 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-58381?
- Check whether anything you run is named in the advisory. 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
A double-free vulnerability exists in GIMP's PSP file format parser within the 'read_layer_block()' function in 'plug-ins/common/file-psp.c'. The flaw is caused by a failure to reset a pointer ('name') to NULL at the start of a processing loop. When a specially crafted PSP file triggers an error (such as a truncated file) during the second iteration of the loop, the 'fread' operation fails before a new memory allocation occurs. This causes the error-handling path to call 'g_free()' on a pointer that was already freed at the end of the previous iteration. An attacker can exploit this via a local attack vector requiring user interaction (opening a file) to cause a denial of service or achieve arbitrary code execution through heap corruption. A fix has been committed to the upstream GNOME GIMP repository.
Affected products
- GNOME GIMP 3.2.1
- Red Hat Red Hat Enterprise Linux 7 affected
- Red Hat Red Hat Enterprise Linux 8 affected
- Red Hat Red Hat Enterprise Linux 9 affected
Timeline
- 2026-07-01: disclosed: Reported to Red Hat Bugzilla
- 2026-07-02: advisory: NVD and Red Hat published advisory details
- 2026-07-02: patched: Upstream fix committed to GNOME GitLab repository