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

Published Sep 3, 2025
·
Updated

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.

Other sources

Write-What-Where in libtiff via TIFFReadRGBAImageOriented

The vulnerability resides in the raster decoding logic of libtiff, specifically when processing paletted (indexed color) images with malformed metadata. The function TIFFReadRGBAImageOriented() computes a pointer offset into the raster buffer based on user-controlled image metadata:

raster + (rheight - img.height) rwidth

If the attacker supplies a very large value for img.height (e.g., 0xFFFF) and a valid rheight (e.g., 256), this computation results in a large positive offset, causing the raster pointer (cp) passed into functions like put8bitcmaptile() or put1bitbwtile() to point beyond the bounds of the allocated buffer.

Inside those functions, memory writes occur like this:

cp++ = PALmap[pp][0];

• The write address (cp) is attacker-controlled via the offset calculation from img.height. • The value written (PALmap[pp][0]) is also attacker-controlled: ◦ pp is dereferenced from pixel data in the image file. ◦ PALmap is constructed from the image's color palette, which the attacker also controls. This constitutes a write-what-where vulnerability with a attacker control. Exploitation of a write-what-where primitive can lead to denial of service or code execution through supply of maliciously crafted files.

Red Hat

Affected Software

4 affected componentsFixes available
LibTIFF libtiff
Microsoft cbl2 libtiff 4.6.0-8
Microsoft azl3 libtiff 4.6.0-8
debian/tiff<=4.2.0-1+deb11u5
4.2.0-1+deb11u84.5.0-6+deb12u44.7.0-3+deb13u24.7.1-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/tiff to a version that resolves this vulnerability.

    Fixed in 4.2.0-1+deb11u8Fixed in 4.5.0-6+deb12u4Fixed in 4.7.0-3+deb13u2Fixed in 4.7.1-2

Event History

Sep 3, 2025
Data Sourced
via Red Hat·03:01 AM
DescriptionSeverityAffected Software
Sep 23, 2025
CVE Published
via MITRE·04:26 PM
Data Sourced
via MITRE·04:26 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Sep 27, 2025
Data Sourced
via Microsoft·01:03 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·01:03 AM
Affected Software
Updated
via Microsoft·01:03 AM
DescriptionSeverity
Sep 30, 2025
Data Sourced
via Ubuntu·11:11 AM
RemedyDescriptionSeverityAffected Software
Jan 30, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
May 29, 2026
Data Sourced
via Debian·06:22 PM
DescriptionAffected Software
Data Sourced
via Launchpad·06:22 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-9900?

CVE-2025-9900 is classified as a critical vulnerability due to its potential to allow arbitrary code execution.

2

How do I fix CVE-2025-9900?

To fix CVE-2025-9900, update to Libtiff version 4.2.0-1+deb11u7 or 4.7.1-1.

3

What software is affected by CVE-2025-9900?

CVE-2025-9900 affects the Libtiff library and specifically versions prior to 4.2.0-1+deb11u7 and 4.7.1-1.

4

What type of vulnerability is CVE-2025-9900?

CVE-2025-9900 is a write-what-where condition that occurs when processing specially crafted TIFF image files.

5

Can CVE-2025-9900 be exploited remotely?

Yes, CVE-2025-9900 can be exploited remotely through malicious TIFF files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203