CVE-2025-8176

What it actually does

Use-after-free in get_histogram function within tools/tiffmedian.c allows local manipulation of heap memory after deallocation during TIFF histogram processing.

Why it matters to the business

Local attackers can crash image processing tools or corrupt memory in workflows handling TIFF files, potentially disrupting graphics, scanning, or document pipelines that depend on LibTIFF.

How an attack unfolds

An attacker crafts a malicious TIFF file and invokes tiffmedian locally on a system with an affected LibTIFF build; the tool's get_histogram routine triggers the use-after-free, enabling memory corruption that may be leveraged for limited local impact.

How to fix it

Update to a build containing commit fe10872e53efba9cc36c66ac4ab3b41a839d5172 or later; rebuild affected tools such as tiffmedian and verify the fix is present before reintroducing TIFF processing workloads.

How to confirm the fix worked

Confirm the installed LibTIFF source or binary contains commit fe10872e53efba9cc36c66ac4ab3b41a839d5172; test tiffmedian with known trigger files and monitor for crashes or unexpected behavior.

Typical attack path

1. Identify or obtain a target system running LibTIFF <= 4.7.0
2. Prepare a specially crafted TIFF image that triggers the vulnerable code path
3. Execute tiffmedian against the crafted file with local privileges
4. Trigger the use-after-free during histogram calculation to achieve memory corruption

How to detect it

Review command-line logs and process execution records for invocations of tiffmedian against untrusted or recently received TIFF files; correlate with any resulting segmentation faults or abnormal memory usage in the same process.

What your security team should do

• Apply the referenced commit to all LibTIFF builds and rebuild dependent packages immediately
• Restrict local execution of tiffmedian and similar tools to trusted users until patched
• Scan internal repositories and build pipelines for references to vulnerable LibTIFF versions