# CVE-2026-112202: Imager::File::GIF versions before 1.006 for Perl allow out-of-bounds reads when consolidating GIF images


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112202, GHSA-v4hp-5h6w-9897, MGASA-2026-0550, UBUNTU-CVE-2026-112202

## What is CVE-2026-112202?

CVE-2026-112202 is a vulnerability, published on 20 Oct 2026. 

### Official description

Imager::File::GIF versions before 1.006 for Perl allow out-of-bounds reads when consolidating GIF images.

With `gif_consolidate => 1`, palette indices from the image are used without checking the colour table's bounds. The i_readgif_low routine reads beyond the heap allocation and copies the bytes into output pixels. The default GIF reader is not affected.

The same code ships bundled in the Imager distribution.

An attacker supplying a crafted GIF can disclose adjacent heap memory through the decoded output and may crash the process.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-112202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112202 is a vulnerability, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112202 in the wild and no public exploit code.

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

## Sources

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

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