# CVE-2026-8454: Memory corruption in Imager::File::GIF

> Attackers can trigger heap out-of-bounds writes via crafted multi-frame GIF files, potentially leading to code execution or crashes in applications using this Perl library.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **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:** No
- **Published:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-8r2w-8p2v-h4g4

## What is CVE-2026-8454?

CVE-2026-8454 is a medium-severity memory corruption vulnerability in TONYC Imager::File::GIF, published on 15 May 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

Imager::File::GIF versions through 1.002 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-8454?

It affects 1 product.


Products: Tonyc Imager\.

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

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

## Is CVE-2026-8454 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8454 is a medium-severity memory corruption vulnerability in TONYC Imager::File::GIF, published on 15 May 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-8454 in the wild and no public exploit code.

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

## Sources

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

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