CVE-2025-9900

8.8

Libtiff · Libtiff

A write-what-where vulnerability in Libtiff allows unauthenticated attackers to trigger memory corruption and potential code execution via a specially crafted TIFF image file.

Executive summary

A critical memory corruption vulnerability in Libtiff can allow unauthenticated remote attackers to achieve arbitrary code execution or cause a denial of service.

Vulnerability

The vulnerability is a write-what-where condition (CWE-123) triggered when processing malformed TIFF metadata. An unauthenticated attacker can supply a crafted image file with an abnormally large height value, forcing the library to write arbitrary data to memory.

Business impact

The flaw carries a CVSS score of 8.8, indicating a high potential for severe impact. Successful exploitation permits an attacker to execute arbitrary code with the privileges of the application processing the image, potentially leading to full system compromise or significant service disruption.

Remediation

Immediate Action: Update Libtiff to version 4.7.1 or apply the specific security errata provided by your distribution vendor (e.g., Red Hat RHSA-2025:17651 and related updates).

Proactive Monitoring: Monitor application logs for segmentation faults or abnormal crash patterns associated with image processing services.

Compensating Controls: Implement file type validation and sanitization at the network perimeter to block malformed TIFF files before they reach vulnerable processing engines.

Exploitation status

Public Exploit Available: No (exploit_available unknown).

Analyst recommendation

Given the potential for arbitrary code execution and the existence of a proof-of-concept, this vulnerability poses a significant risk to any environment that processes untrusted image data. Administrators should prioritize patching Libtiff across all affected systems immediately to prevent potential exploitation.

More Libtiff CVEs

Sources

Originally found and disclosed by Red Hat would like to thank Gareth C (AnchorSec Ltd.) for reporting this issue., per the CVE Program record.