Local memory leak via unclosed first TIFF handle
Published Aug 19, 2025 · Updated Oct 1, 2025
Memory leak in LibTIFF tiffcmp 4.7.0 allows local users to leave allocations unreleased by supplying an unreadable second TIFF file. When TIFFOpen fails for the second input, main returns without calling TIFFClose on the already opened first handle, leaving its parsing allocations for process exit. The condition requires local execution, and the upstream maintainer disputes any security impact because the command-line tool is already exiting.
Summary
What happened
Memory leak in LibTIFF tiffcmp 4.7.0 allows local users to leave allocations unreleased by supplying an unreadable second TIFF file. When TIFFOpen fails for the second input, main returns without calling TIFFClose on the already opened first handle, leaving its parsing allocations for process exit. The condition requires local execution, and the upstream maintainer disputes any security impact because the command-line tool is already exiting.
The record
- CVE
- CVE-2025-9165
- Published
- Aug 19, 2025
- Updated
- Oct 1, 2025
- Vendor
- LibTIFF
- Product
- LibTIFF
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- POC_tiffcmp_memory_leak_abortproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo