Quick answers
- Is CVE-2026-52490 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52490 being exploited in the wild.
- How severe is CVE-2026-52490?
- Critical severity, with a CVSS score of 9.8, published 24 August 2026.
- Which products and versions are affected?
- Libtiff 4.7.1 and earlier.
- Is there a fix for CVE-2026-52490?
- 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-52490 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-52490?
- 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
The vulnerability is an integer overflow in the process_command_opts() function within tools/tiffcrop.c. The -S option accepts cols×rows parameters and checks that their product does not exceed MAX_SECTIONS (32) using unsigned 32-bit multiplication; however, the multiplication itself can overflow (e.g., 65536 × 524288 wraps to 8), causing the validation check to pass while large cols/rows values remain stored in memory. The same vulnerable multiplication is later used in writeImageSections(), allowing an attacker to trigger out-of-bounds memory access. An attacker can exploit this by providing a crafted TIFF file with specific -S parameters, bypassing the bounds check and leading to arbitrary code execution. The vulnerability affects libtiff 4.7.1 and potentially earlier versions.
Affected products
- libtiff libtiff 4.7.1 and earlier
Timeline
- 2026-08-24: disclosed