# CVE-2026-93019: Imager versions before 1.036 for Perl exit the process reading a TGA with a colour map length of 32768 or more in tga_palette_read.

> An attacker can cause a denial of service by providing a crafted TGA image that triggers an integer overflow and subsequent process exit in the Imager Perl library.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93019, GHSA-p4vw-rc54-p2c2, UBUNTU-CVE-2026-93019

## What is CVE-2026-93019?

CVE-2026-93019 is a critical vulnerability, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Imager versions before 1.036 for Perl exit the process reading a TGA with a colour map length of 32768 or more in tga_palette_read.

The reader unpacks the two-byte colour map length into a signed short, so a length of 32768 or more becomes negative. tga_palette_read() casts that value to size_t and asks mymalloc() for a size near SIZE_MAX. The allocation fails and Imager's allocator calls exit(3).

Reading an attacker-supplied file through Imager->read() triggers an uncatchable exit.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value), CWE-196 (Unsigned to Signed Conversion Error)

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


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

Upgrade to a fixed version.

## Is CVE-2026-93019 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93019 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93019 is a critical vulnerability, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93019 exists.

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

## Sources

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

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