CVE-2026-58380 gimp vulnerability
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.
Quick answer
gimp should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 3.2.4
- 7.0
- 8.0
- 9.0
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
GIMP is affected by CVE-2026-58380, a denial-of-service risk. A flaw was found in GIMP's PNM file format parser. The recommended remediation is to update to a GIMP package or distribution update containing the vendor fix for CVE-2026-58380, or the latest vendor-supported fixed GIMP release when available. Until the update is complete, avoid opening untrusted PNM image files and isolate image processing until patched, review logs, and reduce exposure of the affected package, route, provider, or service workflow.
- Inventory every deployment, package, dependency, build runner, integration, route, service, and managed environment that uses GIMP.
- Confirm the installed version/build and compare it with listed affected versions include 3.2.4, 7.0, 8.0, 9.0 and the source advisory for CVE-2026-58380.
- Apply the vendor-supported fix: update to a GIMP package or distribution update containing the vendor fix for CVE-2026-58380, or the latest vendor-supported fixed GIMP release when available.
- If the update cannot be applied immediately, avoid opening untrusted PNM image files and isolate image processing until patched; disable unnecessary public access, package-install paths, file processing, webhooks, message consumers, or high-risk integrations until patched.
- Review application, CI/CD, package manager, container, reverse-proxy, WAF, authentication, route, and audit logs for activity related to CVE-2026-58380.
- Rotate sessions, API tokens, package registry credentials, cloud credentials, webhook secrets, service credentials, and administrator passwords if logs or affected data indicate compromise, credential exposure, or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or build agents when appropriate, and remove temporary files, malicious artifacts, stored payloads, or unsafe configuration created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm GIMP now reports a GIMP package or distribution update containing the vendor fix for CVE-2026-58380, or the latest vendor-supported fixed GIMP release when available or a later vendor-supported fixed release/build for the deployed branch.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-58380, using a safe regression test, dependency inventory, or vendor validation method.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, path traversal, header manipulation, credential exposure, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, dependency check, route regression test, or integration test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup, rebuild, or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-58380?
gimp versions listed as affected should be reviewed: 3.2.4, 7.0, 8.0, 9.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.