CVE-2026-70651: libvips: Possible integer overflow when reading multi-page TIFF images via ImageMagick
libvips is a fast image processing library with low memory needs. Prior to version 8.18.3, libvips built without libtiff support but with ImageMagick support can overflow the combined frame height while loading a crafted multi-page TIFF through VipsForeignLoadMagick. The vulnerable calculations in libvips/foreign/magick6load.c and libvips/foreign/magick7load.c multiply the per-page Ysize by nframes without a checked bound, which can cause a heap buffer over-read and process crash. Most package-manager builds include libtiff and do not use this affected fallback path. This issue is fixed in version 8.18.3.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.18.3
Event History
Frequently Asked Questions
Which deployments are affected by this issue?
Affected deployments are libvips builds without libtiff support that do include ImageMagick support, because they can use the VipsForeignLoadMagick fallback path. Most package-manager builds include libtiff and therefore do not use the affected path.
What does an attacker need to do to trigger the flaw?
An attacker needs to cause the application to load a crafted multi-page TIFF through VipsForeignLoadMagick. The malformed image can overflow the combined frame-height calculation and lead to a heap buffer over-read and process crash.
What can be done if upgrading is not immediately possible?
Avoid processing untrusted multi-page TIFF files through the ImageMagick fallback loader. Using a build with libtiff support avoids the affected fallback path.
How can I determine whether my build needs remediation?
Check whether libvips is older than 8.18.3 and was built with ImageMagick support but without libtiff support. Builds matching those conditions can reach the vulnerable TIFF-loading code.