# CVE-2025-9900: Libtiff: libtiff write-what-where

> Attackers can execute arbitrary code or crash applications by tricking Libtiff into writing data to arbitrary memory locations via crafted TIFF files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Sep 2025
- **Updated:** 29 Jun 2026
- **Also known as:** ALSA-2025:17675, ALSA-2025:19156, ALSA-2025:19276, ALSA-2025:20998, AZL-67722, AZL-67739, AZL-67794, AZL-67803, BELL-CVE-2025-9900, CLSA-2025-1762539974, CLSA-2025-1762544201, CLSA-2025-1762868654, DEBIAN-CVE-2025-9900, DSA-6023-1, ECHO-0ec2-a434-c824, GHSA-qc8j-wvjf-7jfj, OESA-2025-2400, OESA-2025-2401, OESA-2025-2402, OESA-2025-2403, OESA-2025-2404, OESA-2025-2405, RHSA-2025:17651, RHSA-2025:17675, RHSA-2025:17710, RHSA-2025:17738, RHSA-2025:17739, RHSA-2025:17740, RHSA-2025:19156, RHSA-2025:19276, RHSA-2025:19947, RHSA-2025:20998, RHSA-2025:21060, RHSA-2025:21061, RHSA-2025:21062, RHSA-2025:21506, RLSA-2025:17675, RLSA-2025:19156, RLSA-2025:19276, SUSE-SU-2025:3941-1, SUSE-SU-2025:3961-1, UBUNTU-CVE-2025-9900, USN-8347-1, openSUSE-SU-2025:15635-1

## What is CVE-2025-9900?

CVE-2025-9900 is a high-severity memory corruption vulnerability in Red Hat AI Inference Server 3.2, published on 23 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in Libtiff. This vulnerability is a "write-what-where" condition, triggered when the library processes a specially crafted TIFF image file.

By providing an abnormally large image height value in the file's metadata, an attacker can trick the library into writing attacker-controlled color data to an arbitrary memory location. This memory corruption can be exploited to cause a denial of service (application crash) or to achieve arbitrary code execution with the permissions of the user.

Weakness: CWE-123 (Write-what-where Condition)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libtiff` | AlmaLinux:10 | All versions | 4.6.0-6.el10_0.1 |
| `libtiff` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.1 |
| `libtiff-devel` | AlmaLinux:10 | All versions | 4.6.0-6.el10_0.1 |
| `libtiff-devel` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.1 |
| `libtiff-tools` | AlmaLinux:10 | All versions | 4.6.0-6.el10_0.1 |
| `libtiff-tools` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.1 |
| `compat-libtiff3` | AlmaLinux:8 | All versions | 3.9.4-14.el8_10 |
| `libtiff` | AlmaLinux:8 | All versions | 4.0.9-35.el8_10 |
| `libtiff-devel` | AlmaLinux:8 | All versions | 4.0.9-35.el8_10 |
| `libtiff-tools` | AlmaLinux:8 | All versions | 4.0.9-35.el8_10 |
| `libtiff` | Red Hat:enterprise_linux:10.0 | All versions | 0:4.6.0-6.el10_0.1 |
| `libtiff-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:4.6.0-6.el10_0.1 |
| `libtiff-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:4.6.0-6.el10_0.1 |
| `libtiff-devel` | Red Hat:enterprise_linux:10.0 | All versions | 0:4.6.0-6.el10_0.1 |
| `libtiff-tools` | Red Hat:enterprise_linux:10.0 | All versions | 0:4.6.0-6.el10_0.1 |
| `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:4.6.0-6.el10_0.1 |
| `libtiff` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.1 |
| `libtiff-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.1 |
| `libtiff-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.1 |
| `libtiff-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.1 |
| `libtiff-tools` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.1 |
| `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.1 |
| `compat-libtiff3` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-14.el8_10 |
| `compat-libtiff3-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-14.el8_10 |
| `compat-libtiff3-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-14.el8_10 |
| `libtiff` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-35.el8_10 |
| `libtiff-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-35.el8_10 |
| `libtiff-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-35.el8_10 |
| `libtiff-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-35.el8_10 |
| `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-35.el8_10 |
| `libtiff-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-35.el8_10 |
| `libtiff-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-35.el8_10 |
| `libtiff-tools` | Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-35.el8_10 |
| `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-35.el8_10 |
| `compat-libtiff3` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:3.9.4-13.el8_2.1 |
| `libtiff` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:4.0.9-17.el8_2.1 |
| `libtiff-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:4.0.9-17.el8_2.1 |
| `libtiff-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:4.0.9-17.el8_2.1 |
| `libtiff-devel` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:4.0.9-17.el8_2.1 |
| `libtiff-tools-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:4.0.9-17.el8_2.1 |

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

Apply the vendor's patch.

## Is CVE-2025-9900 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9900 is a high-severity memory corruption vulnerability in Red Hat AI Inference Server 3.2, published on 23 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9900 exists.

Affected product: Red Hat AI Inference Server 3.2. 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-9900/ (Markdown: https://insights.sbomify.com/CVE-2025-9900/index.md)
```

## Sources

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

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