CVE-2026-58383

Description

A flaw was found in GIMP's Jeff's Image Format (JIF) parser. A heap-based out-of-bounds write occurs in the ReadJeffsImage() function when a crafted JIF file sets bits-per-pixel to 0, causing the unpack loop to never advance and to write indefinitely past the destination buffer. This could lead to memory corruption, potentially resulting in denial of service or arbitrary code execution.

Statement

A flaw was found in GIMP's Jeff's Image Format (JIF) parser. When a crafted JIF file sets bits-per-pixel to 0, the unpack loop in ReadJeffsImage() never advances and writes past the destination buffer, leading to memory corruption. Successful exploitation requires a user to open a specially crafted JIF file in a build that includes the JIF import path.

Mitigation

None — requires opening a crafted JIF/GIF file.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.3N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionRequiredN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Acknowledgements

Red Hat would like to thank bb1abu for reporting this issue.

Frequently Asked Questions

Want to get errata notifications? Sign up here.