# CVE-2026-93018: Imager versions before 1.036 for Perl disclose uninitialised heap memory reading a paletted image with pixel indexes past its colour map in

> An attacker can disclose process heap memory by supplying a crafted paletted image to the Imager Perl library, potentially exposing sensitive data.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 18 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93018, GHSA-j7v7-cm4g-vrgf, UBUNTU-CVE-2026-93018

## What is CVE-2026-93018?

CVE-2026-93018 is a medium-severity vulnerability, published on 18 Sep 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.036 for Perl disclose uninitialised heap memory reading a paletted image with pixel indexes past its colour map in i_gpix_p and i_glin_p.

The palette is allocated uninitialised, and only the entries a reader adds count as populated. The TGA reader stores pixel indexes without checking them against the colour map. i_gpix_p() rejects only an index greater than the count, so an index equal to it reads the first unpopulated entry, and getpixel() returns it.

i_glin_p() skips any index at or beyond the count without writing that pixel to the caller's buffer. The palette-to-RGB conversion reads each row through an uninitialised buffer, so those pixels of the converted image hold prior heap contents.

Reading an attacker-supplied image through Imager->read() and then fetching its pixels or converting it to RGB discloses process heap memory.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-193 (Off-by-one Error)

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


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

Upgrade to a fixed version.

## Is CVE-2026-93018 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93018 is a medium-severity vulnerability, published on 18 Sep 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-93018 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-93018/ (Markdown: https://insights.sbomify.com/CVE-2026-93018/index.md)
```

## Sources

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

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