CVE-2026-58381
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw was found in GIMP's PSP file format parser. A double-free condition occurs in the read_layer_block() function when processing a specially crafted PSP file. This could allow an attacker to cause memory corruption, potentially leading to denial of service or arbitrary code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGIMP contains a double-free vulnerability in its PSP image file format parser. When processing a specially crafted PSP file, the read_layer_block() function improperly frees the same memory pointer twice, leading to heap corruption. This memory corruption can cause application crashes (denial of service) and potentially enable arbitrary code execution depending on heap state.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm GIMP is installedRun 'gimp --version' or check your package manager for gimp installationsAffected if GIMP is installed on the system
-
Identify installed GIMP versionExecute 'gimp --version' and note the version number shownAffected if The installed version is prior to the patched version that fixes the double-free in read_layer_block()
-
Verify PSP file format support is enabledCheck GIMP's plugin or file format settings - PSP support typically comes via a plugin; look for libpsp or psp in GIMP's plugin directory (often ~/.gimp-2.x/plug-ins/ or /usr/lib/gimp/2.0/plug-ins/)Affected if PSP file format support is loaded/enabled in the GIMP installation
-
Detect PSP files in the environmentSearch for .psp files using 'find / -name "*.psp" 2>/dev/null' or check specific user directoriesAffected if Untrusted or unknown-origin PSP files exist that could be opened with GIMP
-
Review for GIMP crash logsCheck system logs, .gimp-2.x/gimp.log, or crash reports for recent GIMP crashes related to PSP file loadingAffected if GIMP has recently crashed when processing PSP files, indicating possible exploitation
You are affected if GIMP is installed with PSP support enabled and you have an unpatched version that does not contain the fix for the double-free vulnerability in read_layer_block().
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate GIMP to the latest version which should contain a patch fixing the double-free in read_layer_block(). Until patched, avoid opening untrusted PSP files from unknown or untrusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58381 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58381 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data