# CVE-2026-19082: Information disclosure in Imager

> Attackers can read adjacent heap memory by supplying crafted images with zero-count EXIF entries to applications using the Imager Perl library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-19082, GHSA-hx46-55wp-hv6m, MGASA-2026-0394, UBUNTU-CVE-2026-19082

## What is CVE-2026-19082?

CVE-2026-19082 is a high-severity vulnerability in TONYC Imager, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Imager versions from 0.45_02 before 1.034 for Perl may expose adjacent heap bytes via strlen() over-read from zero-count ASCII EXIF entries in copy_string_tags.

copy_string_tags() computes an ASCII EXIF tag's length as `entry->size - 1` to strip the trailing NUL. A zero-count ASCII entry sets `entry->size` to 0, and the derived length reaches i_tags_add() as -1, which is interpreted as a request to call strlen(), scanning past the entry to the next NUL and copying those bytes into the tag. JPEG reaches this path via im_decode_exif(), as does the separate Imager::File::WEBP distribution, which is fixed by upgrading Imager.

Any caller of Imager->read() on an attacker-supplied image with such an entry may receive an exif_* tag holding adjacent heap bytes instead of an empty string.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-19082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19082 is a high-severity vulnerability in TONYC Imager, published on 7 Aug 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-19082 exists.

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

## Sources

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

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