Enterprise LinuxOperating system · Redhat
CVE-2026-58384
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 PSD parser. An integer overflow in read_RLE_channel() can cause an undersized heap allocation for the RLE row-length table, after which subsequent per-row writes corrupt heap memory. This could lead to memory corruption, potentially resulting in 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 · moderate confidenceGIMP's PSD parser contains an integer overflow vulnerability in the read_RLE_channel() function. When parsing RLE-compressed Photoshop files, the function calculates an undersized heap buffer for the row-length table due to integer overflow, leading to heap corruption when subsequent per-row writes occur.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise LinuxOperating system
= 9.0= 3.2.4CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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 'rpm -qa | grep -i gimp' on RHEL/CentOS or 'dpkg -l | grep -i gimp' on Debian-based systems, or check for gimp in your package managerAffected if GIMP is installed and matches version 3.2.4 on RHEL 9.0 or falls within the affected version range
-
Confirm GIMP version numberRun 'gimp --version' or check the package version via your system's package manager (rpm -q gimp or dpkg -s gimp)Affected if The installed version equals 3.2.4 on RHEL 9.0 or is an unpatched version that contains the vulnerable PSD parser code
-
Identify if PSD files are processedCheck recent file open operations or examine file association configurations for .psd files associated with GIMP. Look for PSD files in recent directories or check 'gimp -h' for file-related usage patternsAffected if Users routinely open or process RLE-compressed .psd (Photoshop) files using the vulnerable GIMP installation
-
Verify the PSD plugin/module is availableCheck for the presence of the PSD file handling module in the GIMP plugin directory (typically /usr/lib/gimp/2.0/plug-ins/ or similar path) or run 'gimp --new-instance' and attempt to open a PSD fileAffected if The PSD file format plugin exists and is loadable, enabling the vulnerable read_RLE_channel() code path
You are affected if GIMP version 3.2.4 on RHEL 9.0 (or an unpatched version within the affected range) is installed and configured to handle RLE-compressed PSD files, as the integer overflow in read_RLE_channel() will trigger during PSD parsing.
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 patched version. Avoid opening untrusted PSD files with vulnerable GIMP versions until patched.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing5.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 $4,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58384 — 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-58384 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