dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2026-58380

HIGH · 7.8 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Public exploit No privileges 7 weeks old

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 · unedited
A flaw was found in GIMP's PNM file format parser. When parsing a specially crafted PNM file, the pnmscanner_gettoken() function writes a null terminator one byte past the end of a stack-allocated buffer due to an off-by-one error in the loop boundary check. 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 · high confidence

An off-by-one buffer overflow exists in GIMP's PNM file format parser in the pnmscanner_gettoken() function. The loop boundary check incorrectly allows writing a null terminator one byte past the end of a stack-allocated buffer when parsing specially crafted PNM files, leading to stack-based memory corruption that could enable denial of service or potentially arbitrary code execution.

MitigationUntil an official patch is available, avoid opening untrusted PNM files in GIMP. Consider using file parsing libraries with bounds checking or sandboxing PNM processing. Apply vendor patches immediately when released.

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
Affected:= 7.0= 8.0= 9.0
GimpApplication
Affected:= 3.2.4

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GIMP version
    Run 'gimp --version' or query package manager (e.g., 'rpm -q gimp' on RHEL-based systems) to determine the installed GIMP version
    Affected if Version is 3.2.4 or falls within the affected RHEL versions (7.0, 8.0, 9.0) that ship GIMP 3.2.4
  2. Verify PNM file format plugin is present
    Locate GIMP's plugin directory (typically /usr/lib64/gimp/2.0/plug-ins/ or /usr/lib/gimp/2.0/plug-ins/) and search for pnm-related plugin files such as 'file-pnm', 'pnm', or 'libpnmscanner'
    Affected if PNM plugin file exists in GIMP's plugin directory, indicating PNM format support is enabled
  3. Check for pnmscanner source or binary
    Search for files named 'pnmscanner.c', 'pnmscanner', or 'libpnmscanner' within the GIMP installation directories: 'find /usr -name "*pnmscanner*" 2>/dev/null'
    Affected if The pnmscanner component is present, confirming the vulnerable code path exists in the environment
  4. Inspect PNM file handler registration
    Check GIMP's registered file handlers: look for 'PNM' or 'PNM/PPM/PGM/PBM' in GIMP's procedure database (gimp --batch '(gimp-procedural-db-dump)' 2>/dev/null | grep -i pnm) or examine file-usr-install.c and related plugin registration files
    Affected if PNM file format handler is registered and loadable, meaning GIMP can parse PNM files and the vulnerable parser code can be invoked

If GIMP version 3.2.4 (or the RHEL 7.0/8.0/9.0 variants) is installed AND the PNM plugin/handler is present and enabled, the environment is vulnerable to CVE-2026-58380 when processing untrusted PNM files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until an official patch is available, avoid opening untrusted PNM files in GIMP. Consider using file parsing libraries with bounds checking or sandboxing PNM processing. Apply vendor patches immediately when released.

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58380 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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