cve.bz

CVE-2026-6695

5.5 mediumEPSS 0.3%

Medium (5.5). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in GIMP. A remote attacker could exploit this by tricking a user into opening a specially crafted PAA (Paint Shop Pro Array) image file. This vulnerability, a heap-based out-of-bounds write in the decode_lzss() function of the PAA file format plugin, allows data to be written beyond the intended memory buffer. This could lead to heap metadata corruption and potentially enable the attacker to execute arbitrary code on the affected system.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-805 Buffer Access with Incorrect Length Value
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-6695 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-6695?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-6695?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-6695 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
redhat:enterprise_linux6.0
redhat:enterprise_linux7.0
redhat:enterprise_linux8.0
redhat:enterprise_linux9.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14gimp3.2.4-1DEBIAN-CVE-2026-6695
Ubuntu26.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 3 moregimpno fix listedUBUNTU-CVE-2026-6695

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

An Important heap-based out-of-bounds write vulnerability exists in the PAA file format plugin of GIMP. This flaw allows an attacker to achieve potential remote code execution by tricking a user into opening a specially crafted .paa file. Red Hat Enterprise Linux systems where GIMP is installed and used to process untrusted image files are affected.

Red Hat's mitigation

To mitigate this issue, users should avoid opening .paa files from untrusted sources. If GIMP is not required, consider removing the `gimp` package to eliminate the attack vector. Removing the `gimp` package may also remove other desktop-related packages that depend on it.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6gimpFix deferred
Red Hat Enterprise Linux 7gimpFix deferred
Red Hat Enterprise Linux 8gimp:2.8/gimpFix deferred
Red Hat Enterprise Linux 9gimpFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-6695.

Attack patterns (CAPEC)

  • CAPEC-100 Overflow Buffers Likelihood: High · Severity: Very High
  • CAPEC-256 SOAP Array Overflow Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON