Vulnerabilities · 2025 · Libtiff
CVE-2025-9165
Libtiff vulnerability
A flaw has been found in LibTIFF 4.7.0. This affects the function _TIFFmallocExt/_TIFFCheckRealloc/TIFFHashSetNew/InitCCITTFax3 of the file tools/tiffcmp.c of the component tiffcmp. Executing manipulation can lead to memory leak. The attack is restricted to local execution. This attack is characterized by high complexity. It is indicated that the exploitability is difficult. The exploit has been published and may be used. There is ongoing doubt regarding the real existence of this vulnerability. This patch is called ed141286a37f6e5ddafb5069347ff5d587e7a4e0. It is best practice to apply a patch to resolve this issue. A researcher disputes the security impact of this issue, because "this is a memory leak on a command line tool that is about to exit anyway". In the reply the project maintainer declares this issue as "a simple 'bug' when leaving the command line tool and (...) not a security issue at all".
Affected products
Libtiff. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Libtiff runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- gitlab.com/libtiff/libtiff/-/issues/728 · Exploit
- gitlab.com/libtiff/libtiff/-/merge_requests/747 · Patch
- gitlab.com/libtiff/libtiff/-/issues/728#note_2709263214 · Exploit
- gitlab.com/libtiff/libtiff/-/commit/ed141286a37f6e5ddafb5069347ff5d587e7a4e0 · Patch
- vuldb.com/?id.320543 · Third Party Advisory
- vuldb.com/?submit.630506 · Third Party Advisory
- vuldb.com/?submit.630507 · Third Party Advisory
- drive.google.com/file/d/1FWhmkzksH8-qU0ZM6seBzGNB3aPnX3G8/view?usp=sharing · Exploit
- nvd.nist.gov/vuln/detail/CVE-2025-9165
- cve.org/CVERecord?id=CVE-2025-9165
More vulnerabilities in Libtiff products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.