Quick answers
- Is CVE-2026-52492 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52492 being exploited in the wild.
- How severe is CVE-2026-52492?
- High severity, with a CVSS score of 7.8, published 24 August 2026.
- Which products and versions are affected?
- Libtiff prior to commit 94affc5c (released December 29, 2025).
- Is there a fix for CVE-2026-52492?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-52492 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-52492?
- Check whether you run Libtiff at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow exists in the libtiff rgb2ycbcr utility's cvtRaster() function when computing strip buffer sizes for YCbCr color space conversion. The vulnerability occurs during size calculations for heap allocation, resulting in an undersized buffer that is subsequently written to during TIFF image processing. An attacker can craft a malicious TIFF image to trigger the integer overflow, leading to a heap-based buffer overflow. This requires local access and user interaction (opening the malicious TIFF file), but can result in information disclosure, denial of service, or code execution. A fix is available in commit 94affc5c which adds conversion warnings to catch such issues.
Affected products
- libtiff libtiff prior to commit 94affc5c (released December 29, 2025)
Timeline
- 2026-08-24: disclosed: CVE published
- 2025-12-29: other: Fix commit 94affc5c merged