# CVE-2026-8669: Imager versions through 1.030 for Perl allow a heap out of bounds (OOB) write on crafted multi-frame GIF files

> A heap out-of-bounds write in the Perl Imager library allows attackers to execute arbitrary code or cause denial of service via crafted multi-frame GIF files.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** DEBIAN-CVE-2026-8669, GHSA-6275-mpwc-pq3g, MGASA-2026-0154, UBUNTU-CVE-2026-8669

## What is CVE-2026-8669?

CVE-2026-8669 is a medium-severity memory corruption vulnerability in TONYC Imager, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Imager versions through 1.030 for Perl allow a heap out of bounds (OOB) write on crafted multi-frame GIF files.

Imager::File::GIF's i_readgif_multi_low allocates a single per-row buffer GifRow sized for the GIF's global screen width 'SWidth' and reuses it across every image in the file.

The page-match branch validates Image.Width + Image.Left > SWidth before each DGifGetLine write, but the parallel skip-image branch at imgif.c:790-805 calls DGifGetLine(GifFile, GifRow, Width) with no such check.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-8669 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8669 is a medium-severity memory corruption vulnerability in TONYC Imager, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8669 in the wild and no public exploit code.

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

## Sources

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

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