# CVE-2026-13705: Memory corruption in Imager

> A heap out-of-bounds read in the Imager Perl library allows attackers to crash the application by processing a crafted SGI image.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-13705, GHSA-pmgh-mrwc-qw67, UBUNTU-CVE-2026-13705

## What is CVE-2026-13705?

CVE-2026-13705 is a high-severity memory corruption vulnerability in TONYC Imager, published on 6 Jul 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 versions before 1.032 for Perl have a heap out-of-bounds read in the bundled Imager::File::SGI reader via a 16-bit RLE literal run in read_rgb_16_rle.

read_rgb_16_rle guards each literal run with if (count > data_left), but count is a pixel count while every 16-bit sample consumes two bytes. The copy loop reads inp[0] * 256 + inp[1] and advances two bytes per pixel, so a run with data_left / 2 < count <= data_left passes the guard yet consumes 2 * count bytes and reads past the end of the buffer. The 8-bit path is unaffected because there one pixel is one byte.

Reading a crafted SGI image through Imager->read triggers the over-read before the parser rejects the malformed image, which can crash the process.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-13705 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13705 is a high-severity memory corruption vulnerability in TONYC Imager, published on 6 Jul 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-13705 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-13705/ (Markdown: https://insights.sbomify.com/CVE-2026-13705/index.md)
```

## Sources

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

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