# CVE-2026-52491: Integer overflow in n/a

> An integer overflow in libtiff's thumbnail tool allows attackers to execute arbitrary code via crafted images.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** AZL-98204, DEBIAN-CVE-2026-52491, ECHO-c81e-9900-f4e2, GHSA-28v3-93mm-ccfv

## What is CVE-2026-52491?

CVE-2026-52491 is a high-severity vulnerability in n/a, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the libtiff/tools/thumbnail.c: main() component

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-52491 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52491 is a high-severity vulnerability in n/a, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-52491 in the wild and no public exploit code.

Affected product: n/a. 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-52491/ (Markdown: https://insights.sbomify.com/CVE-2026-52491/index.md)
```

## Sources

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

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