Memory corruption via stale PSP layer-name pointer
Published Jul 2, 2026 · Updated Jul 2, 2026
Double-free in GIMP's PSP parser on Red Hat Enterprise Linux 7, 8, and 9 allows attackers to corrupt memory via a crafted PSP file. In read_layer_block(), a second-iteration fread error occurs before name is reallocated, leaving the first iteration's freed pointer to reach g_free again. A user must open or import the crafted file; the resulting corruption can crash GIMP or execute code with that user's privileges.
Summary
What happened
Double-free in GIMP's PSP parser on Red Hat Enterprise Linux 7, 8, and 9 allows attackers to corrupt memory via a crafted PSP file. In read_layer_block(), a second-iteration fread error occurs before name is reallocated, leaving the first iteration's freed pointer to reach g_free again. A user must open or import the crafted file; the resulting corruption can crash GIMP or execute code with that user's privileges.
The record
- CVE
- CVE-2026-58381
- Published
- Jul 2, 2026
- Updated
- Jul 2, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 7
- Classifications
- CWE-415, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 2, 2026CVE publishedPublication date reported by the CVE source.
- Jul 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo