CVE-2025-9900
published 2025-09-23CVE-2025-9900: 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…
PriorityP350high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
0.74%
49.9th percentile
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.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | tiff | < tiff 4.5.0-6+deb12u3 (bookworm) | tiff 4.5.0-6+deb12u3 (bookworm) |
| msrc | azl3_libtiff_4.6.0-8_on_azure_linux_3.0 | — | — |
| msrc | cbl2_libtiff_4.6.0-8_on_cbl_mariner_2.0 | — | — |
| ubuntu | gdal | — | — |
| ubuntu | qtwebengine-opensource-src | — | — |
| ubuntu | texmaker | — | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
osv8.8HIGH
vendor_debian8.8HIGH
vendor_msrc8.8HIGH
vendor_oracle8.8HIGH
vendor_redhat8.8HIGH
vendor_ubuntu3.3LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
GDAL vulnerability
vendor_ubuntu·2026-05-28
CVE-2025-9900 GDAL vulnerability
Title: GDAL vulnerability
Summary: GDAL could be made to crash or run programs if it received specially
crafted input.
It was discovered that the vendored LibTIFF in GDAL incorrectly handled
memory when parsing malformed TIFF image metadata. An attacker could
possibly use this issue to cause a denial of service, obtain sensitive
information, or execute arbitrary code.
Instructions: In general, a standard system update will make all the necessary changes.
Ubuntu
QT WebEngine vulnerability
vendor_ubuntu·2026-05-28
CVE-2025-9900 QT WebEngine vulnerability
Title: QT WebEngine vulnerability
Summary: QT WebEngine could be made to crash or run programs if it received specially
crafted input.
It was discovered that the vendored LibTIFF in QT WebEngine incorrectly
handled memory when parsing malformed TIFF image metadata. An attacker
could possibly use this issue to cause a denial of service, obtain
sensitive information, or execute arbitrary code.
Instructions: In general, a standard system update will make all the necessary changes.
Ubuntu
Texmaker vulnerabilities
vendor_ubuntu·2026-05-28
CVE-2025-9900 Texmaker vulnerabilities
Title: Texmaker vulnerabilities
Summary: Texmaker could be made to crash or run programs if it received specially
crafted input.
It was discovered that the vendored LibTIFF in Texmaker incorrectly
handled memory when parsing malformed TIFF image metadata. An attacker
could possibly use this issue to cause a denial of service, obtain
sensitive information, or execute arbitrary code.
Instructions: In general, a standard system update will make all the necessary changes.
Oracle
Oracle Oracle Communications Risk Matrix: Configuration Management Platform (LibTIFF) — CVE-2025-9900
vendor_oracle·2026-01-15·CVSS 8.8
CVE-2025-9900 [HIGH] Oracle Oracle Communications Risk Matrix: Configuration Management Platform (LibTIFF) — CVE-2025-9900
Oracle Oracle Communications Risk Matrix: Configuration Management Platform (LibTIFF) vulnerability
CVE: CVE-2025-9900
CVSS: 8.8
Protocol: HTTP
Remote exploit: Yes
Affected versions: Network
Advisory: cpujan2026 (JAN 2026)
Ubuntu
LibTIFF vulnerabilities
vendor_ubuntu·2025-09-29·CVSS 3.3
CVE-2025-9900 [LOW] LibTIFF vulnerabilities
Title: LibTIFF vulnerabilities
Summary: Several security issues were fixed in LibTIFF.
Xudong Cao and Yuqing Zhang discovered that LibTIFF incorrectly handled
memory when parsing malformed TIFF images. An attacker could possibly use
this issue to cause LibTIFF to crash, resulting in a denial of service.
(CVE-2025-8961)
Xudong Cao and Yuqing Zhang discovered that LibTIFF incorrectly handled
memory when parsing malformed TIFF image headers. An attacker could
possibly use this issue to cause LibTIFF to leak memory, resulting in a
denial of service. (CVE-2025-9165)
It was discovered that LibTIFF incorrectly handled memory when parsing
malformed TIFF image metadata. An attacker could possibly use this issue to
cause a denial of service, obtain sensitive information, or execute
arbitrary cod
Red Hat
libtiff: Libtiff Write-What-Where
vendor_redhat·2025-09-22·CVSS 8.8
CVE-2025-9900 [HIGH] CWE-123 libtiff: Libtiff Write-What-Where
libtiff: Libtiff Write-What-Where
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.
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
Microsoft
Libtiff: libtiff write-what-where
vendor_msrc·2025-09-09·CVSS 8.8
CVE-2025-9900 [HIGH] CWE-123 Libtiff: libtiff write-what-where
Libtiff: libtiff write-what-where
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
redhat: redhat
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://learn.microsoft.com/en-us
Debian
CVE-2025-9900: tiff - A flaw was found in Libtiff. This vulnerability is a "write-what-where" conditio...
vendor_debian·2025·CVSS 8.8
CVE-2025-9900 [HIGH] CVE-2025-9900: tiff - A flaw was found in Libtiff. This vulnerability is a "write-what-where" conditio...
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.
Scope: local
bookworm: resolved (fixed in 4.5.0-6+deb12u3)
bullseye: resolved (fixed in 4.2.0-1+deb11u7)
forky: resolved (fixed in 4.7.1-1)
sid: resolved (fixed in 4.7.1-1)
trixie: resolved (fixed in 4.7.0-3+deb13u1)
OSV
tiff vulnerabilities
osv·2025-09-29·CVSS 4.8
CVE-2025-8961 [MEDIUM] tiff vulnerabilities
tiff vulnerabilities
Xudong Cao and Yuqing Zhang discovered that LibTIFF incorrectly handled
memory when parsing malformed TIFF images. An attacker could possibly use
this issue to cause LibTIFF to crash, resulting in a denial of service.
(CVE-2025-8961)
Xudong Cao and Yuqing Zhang discovered that LibTIFF incorrectly handled
memory when parsing malformed TIFF image headers. An attacker could
possibly use this issue to cause LibTIFF to leak memory, resulting in a
denial of service. (CVE-2025-9165)
It was discovered that LibTIFF incorrectly handled memory when parsing
malformed TIFF image metadata. An attacker could possibly use this issue to
cause a denial of service, obtain sensitive information, or execute
arbitrary code. (CVE-2025-9900)
OSV
CVE-2025-9900: A flaw was found in Libtiff
osv·2025-09-23·CVSS 8.8
CVE-2025-9900 [HIGH] CVE-2025-9900: A flaw was found in Libtiff
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.
GHSA
GHSA-qc8j-wvjf-7jfj: A flaw was found in Libtiff
ghsa_unreviewed·2025-09-23
CVE-2025-9900 [HIGH] CWE-123 GHSA-qc8j-wvjf-7jfj: A flaw was found in Libtiff
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2025-9900 tkimg: Libtiff Write-What-Where [fedora-42]
bugzilla·2025-12-18·CVSS 8.8
CVE-2025-9900 [HIGH] CVE-2025-9900 tkimg: Libtiff Write-What-Where [fedora-42]
CVE-2025-9900 tkimg: Libtiff Write-What-Where [fedora-42]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
Discussion:
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are
Bugzilla
CVE-2025-9900 iv: Libtiff Write-What-Where [fedora-42]
bugzilla·2025-12-18·CVSS 8.8
CVE-2025-9900 [HIGH] CVE-2025-9900 iv: Libtiff Write-What-Where [fedora-42]
CVE-2025-9900 iv: Libtiff Write-What-Where [fedora-42]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
Discussion:
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no
Bugzilla
CVE-2025-9900 libtiff: Libtiff Write-What-Where [fedora-42]
bugzilla·2025-12-18·CVSS 8.8
CVE-2025-9900 [HIGH] CVE-2025-9900 libtiff: Libtiff Write-What-Where [fedora-42]
CVE-2025-9900 libtiff: Libtiff Write-What-Where [fedora-42]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
Discussion:
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that a
Bugzilla
CVE-2025-9900 mingw-libtiff: Libtiff Write-What-Where [fedora-42]
bugzilla·2025-12-18·CVSS 8.8
CVE-2025-9900 [HIGH] CVE-2025-9900 mingw-libtiff: Libtiff Write-What-Where [fedora-42]
CVE-2025-9900 mingw-libtiff: Libtiff Write-What-Where [fedora-42]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
Discussion:
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases
Bugzilla
CVE-2025-9900 libtiff: Libtiff Write-What-Where
bugzilla·2025-09-03·CVSS 8.8
CVE-2025-9900 [HIGH] CVE-2025-9900 libtiff: Libtiff Write-What-Where
CVE-2025-9900 libtiff: Libtiff Write-What-Where
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:
https://access.redhat.com/errata/RHSA-2025:17651https://access.redhat.com/errata/RHSA-2025:17675https://access.redhat.com/errata/RHSA-2025:17710https://access.redhat.com/errata/RHSA-2025:17738https://access.redhat.com/errata/RHSA-2025:17739https://access.redhat.com/errata/RHSA-2025:17740https://access.redhat.com/errata/RHSA-2025:19113https://access.redhat.com/errata/RHSA-2025:19156https://access.redhat.com/errata/RHSA-2025:19276https://access.redhat.com/errata/RHSA-2025:19906https://access.redhat.com/errata/RHSA-2025:19947https://access.redhat.com/errata/RHSA-2025:20956https://access.redhat.com/errata/RHSA-2025:20998https://access.redhat.com/errata/RHSA-2025:21060https://access.redhat.com/errata/RHSA-2025:21061https://access.redhat.com/errata/RHSA-2025:21062https://access.redhat.com/errata/RHSA-2025:21407https://access.redhat.com/errata/RHSA-2025:21506https://access.redhat.com/errata/RHSA-2025:21507https://access.redhat.com/errata/RHSA-2025:21508https://access.redhat.com/errata/RHSA-2025:21994https://access.redhat.com/errata/RHSA-2025:23078https://access.redhat.com/errata/RHSA-2025:23079https://access.redhat.com/errata/RHSA-2025:23080https://access.redhat.com/errata/RHSA-2026:0001https://access.redhat.com/errata/RHSA-2026:0076https://access.redhat.com/errata/RHSA-2026:0077https://access.redhat.com/errata/RHSA-2026:0078https://access.redhat.com/errata/RHSA-2026:3461https://access.redhat.com/errata/RHSA-2026:3462https://access.redhat.com/errata/RHSA-2026:7504https://access.redhat.com/security/cve/CVE-2025-9900https://bugzilla.redhat.com/show_bug.cgi?id=2392784https://github.com/SexyShoelessGodofWar/LibTiff-4.7.0-Write-What-Where?tab=readme-ov-filehttps://gitlab.com/libtiff/libtiff/-/issues/704https://gitlab.com/libtiff/libtiff/-/merge_requests/732https://libtiff.gitlab.io/libtiff/releases/v4.7.1.htmlhttp://www.openwall.com/lists/oss-security/2025/09/26/3https://lists.debian.org/debian-lts-announce/2025/09/msg00031.htmlhttps://github.com/SexyShoelessGodofWar/LibTiff-4.7.0-Write-What-Where?tab=readme-ov-file
2025-09-23
Published