# CVE-2026-90947: Gimp: gimp: out-of-bounds write in lighting effects plugin via crafted preset file

> An attacker can achieve arbitrary code execution or cause a crash by tricking a user into opening a malicious lighting preset file in GIMP.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-90947, GHSA-pcjr-j975-j4c4, UBUNTU-CVE-2026-90947

## What is CVE-2026-90947?

CVE-2026-90947 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 6, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in GIMP. When processing a specially crafted lighting preset file, the Lighting Effects filter does not properly validate the number of light sources. This can lead to an out-of-bounds write, corrupting memory. An attacker could exploit this by convincing a user to open a malicious preset file, potentially causing a crash or enabling arbitrary code execution.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-90947?


## How do I fix CVE-2026-90947?

Apply the vendor's patch.

## Is CVE-2026-90947 being exploited?

There is no known exploitation of CVE-2026-90947 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90947 and fix it if it is affected.

What it is: CVE-2026-90947 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 6, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-90947 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90947/ (Markdown: https://insights.sbomify.com/CVE-2026-90947/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90947
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90947
- OSV: https://osv.dev/vulnerability/CVE-2026-90947

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90947/
Summaries are generated and may contain mistakes; the official description above is the record.