CVE-2026-58380

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-06 15:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-11-05 23:16 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 7.3 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-07-06 15:16 UTC

Last modified

2026-11-05 23:16 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-193

Record status

Undergoing Analysis

Affected

• Gimp 3.2.4
• Redhat Enterprise Linux 7.0
• Redhat Enterprise Linux 8.0
• Redhat Enterprise Linux 9.0

Attack profile CVSS 3.1 · 7.3

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-58380.md and follow it. Check whether this project is affected by CVE-2026-58380. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge