Utility crash via aliased cleanup buffers
Published Feb 23, 2026 · Updated Feb 23, 2026
Double free in libtiff tiffcrop 4.7.1 and earlier allows local users to crash the utility by processing a crafted TIFF image. On an image-inversion failure, the cleanup path aliases read_buff and crop_buff, then frees the same allocation through both pointers. The malformed image must reach tiffcrop with color inversion enabled; allocator checks abort the process, so the demonstrated impact is a utility crash.
Summary
What happened
Double free in libtiff tiffcrop 4.7.1 and earlier allows local users to crash the utility by processing a crafted TIFF image. On an image-inversion failure, the cleanup path aliases read_buff and crop_buff, then frees the same allocation through both pointers. The malformed image must reach tiffcrop with color inversion enabled; allocator checks abort the process, so the demonstrated impact is a utility crash.
The record
- CVE
- CVE-2025-61145
- Published
- Feb 23, 2026
- Updated
- Feb 23, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 23, 2026CVE publishedPublication date reported by the CVE source.
- Feb 23, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- POC_tiffcrop_double_free_corruption_topproof 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