# CVE-2026-133007: Gimp: gimp: uninitialized stack disclosure in xcf tile loader


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-cfvw-fcxc-pcw8

## What is CVE-2026-133007?

CVE-2026-133007 is a medium-severity vulnerability in gimp, published on 19 Nov 2026. 

### Official description

A flaw was found in GIMP. Opening a crafted XCF with a truncated uncompressed tile can expose uninitialized main-process stack memory through the imported layer's pixel data, which may include process addresses that weaken ASLR.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 1 product.


Products: Red Hat Enterprise Linux.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:redhat:enterprise_linux:10:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:enterprise_linux:9:*:*:*:*:*:*:*`

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

No fix has been published for CVE-2026-133007 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-133007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133007 is a medium-severity vulnerability in gimp, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133007 in the wild and no public exploit code.

Affected product: gimp. 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-133007/ (Markdown: https://insights.sbomify.com/CVE-2026-133007/index.md)
```

## Sources

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

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