Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-40916

5.0 · MEDIUM

A flaw was found in GIMP.

Published Apr 15, 2026CWE-787EPSS 0.22%

Overview

CVE-2026-40916 is a medium-severity vulnerability. It was published on April 15, 2026 and has a CVSS 3.1 base score of 5.0 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.0, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

A flaw was found in GIMP. A stack buffer overflow vulnerability in the TIM image loader's 4BPP decoding path allows a local user to cause a Denial of Service (DoS). By opening a specially crafted TIM image file, the application crashes due to an unconditional overflow when writing to a variable-length array.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refaccess.redhat.com/security/cve/CVE-2026-40916Refbugzilla.redhat.com/show_bug.cgi?id=2458745

How CyberStrike helps

Frequently asked questions

What is CVE-2026-40916?

CVE-2026-40916 is a medium-severity vulnerability. It was published on April 15, 2026 and has a CVSS 3.1 base score of 5.0 (MEDIUM).

How severe is CVE-2026-40916?

This vulnerability has a CVSS 3.1 base score of 5.0, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-40916?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-40916?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-40916 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999