CVE-2026-58379
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 Paint Shop Pro (PSP) file format parser. This heap buffer overflow vulnerability allows a remote attacker to cause arbitrary code execution or a denial of service (DoS) by tricking a user into opening a specially crafted PSP image file. The vulnerability occurs because the software incorrectly calculates buffer sizes when processing low bit-depth images, leading to an overwrite of adjacent memory.
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 · moderate confidenceGIMP's Paint Shop Pro (PSP) file format parser contains a heap buffer overflow vulnerability caused by incorrect buffer size calculations when processing low bit-depth images. When parsing specially crafted PSP files, the parser allocates an undersized buffer based on faulty size computation, allowing adjacent memory to be overwritten. This can lead to arbitrary code execution or denial of service when a user opens a malicious PSP file.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/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.
-
Verify GIMP is installedRun 'gimp --version' or check for GIMP in your installed applicationsAffected if GIMP is not installed means this CVE does not apply to your environment
-
Identify installed GIMP versionExecute 'gimp --version' or check your package manager (apt list --installed | grep gimp, rpm -q gimp, etc.)Affected if Your version falls within any unpatched version range for CVE-2026-58379 - compare your version to official GIMP release notes for patch status
-
Confirm PSP file support existsCheck if GIMP's PSP plug-in or file loader is present - look for 'file-psp' in your GIMP plug-ins directory (typically /usr/lib/gimp/*/plug-ins/ or ~/.gimp-*/plug-ins/)Affected if The PSP loader plug-in exists and is enabled, meaning GIMP can parse PSP files and is vulnerable when opening malicious PSP files
-
Test PSP file import capabilityAttempt to open a benign PSP file in GIMP or check file format support via GIMP's preferences (XCF > Preferences > File Handling > File Filters)Affected if PSP appears as an enabled file format, confirming the vulnerable parser can be invoked on your system
You are affected if GIMP with an unpatched version is installed and the PSP file format loader is enabled - opening a specially crafted PSP file could trigger the heap buffer overflow.
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 dataAvoid opening untrusted or unknown PSP files in GIMP until an official patch is released. Consider implementing file type restrictions or sandboxing for GIMP in enterprise environments as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58379 — 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-58379 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