# CVE-2025-8851: LibTIFF tiffcrop tiffcrop.c readSeparateStripsetoBuffer stack-based overflow

> A stack-based buffer overflow in LibTIFF's tiffcrop tool allows local attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2025
- **Updated:** 12 Aug 2025
- **Also known as:** AZL-66258, AZL-66282, CLSA-2026-1787932569, DEBIAN-CVE-2025-8851, ECHO-0263-9519-53e9, GHSA-mcqf-6qjh-v78v, JLSEC-2025-321, MINI-mx84-v38v-m9cj, ROOT-OS-DEBIAN-12-CVE-2025-8851, SUSE-SU-2025:3989-1, UBUNTU-CVE-2025-8851, openSUSE-SU-2025:15682-1

## What is CVE-2025-8851?

CVE-2025-8851 is a medium-severity memory corruption vulnerability in Libtiff Libtiff, published on 11 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in LibTIFF up to 4.5.1. Affected by this issue is the function readSeparateStripsetoBuffer of the file tools/tiffcrop.c of the component tiffcrop. The manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The patch is identified as 8a7a48d7a645992ca83062b3a1873c951661e2b3. It is recommended to apply a patch to fix this issue.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-8851?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tiff` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 4.0.9-44.106.1 |
| `tiff` | openSUSE:Tumbleweed | All versions | 4.7.1-3.1 |

Products: Libtiff Libtiff.

## How do I fix CVE-2025-8851?

Apply the vendor's patch.

## Is CVE-2025-8851 being exploited?

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

## Other vulnerabilities in Libtiff Libtiff

- [CVE-2004-1308](https://insights.sbomify.com/CVE-2004-1308/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0929](https://insights.sbomify.com/CVE-2004-0929/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-61144](https://insights.sbomify.com/CVE-2025-61144/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9533](https://insights.sbomify.com/CVE-2016-9533/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9534](https://insights.sbomify.com/CVE-2016-9534/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8851 and fix it if it is affected.

What it is: CVE-2025-8851 is a medium-severity memory corruption vulnerability in Libtiff Libtiff, published on 11 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8851 exists.

Affected product: Libtiff Libtiff. 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-2025-8851/ (Markdown: https://insights.sbomify.com/CVE-2025-8851/index.md)
```

## Sources

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

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