Quick answers
- Is CVE-2026-69242 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69242 being exploited in the wild.
- How severe is CVE-2026-69242?
- Informational severity, published 20 August 2026.
- Which products and versions are affected?
- Libvips before 8.18.3.
- Is there a fix for CVE-2026-69242?
- A patch was published on 2026-04-26. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-69242 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-69242?
- Check whether you run Libvips 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 vulnerability exists in libvips' VipsForeignLoadTiff function when processing many-band TIFF files. The vulnerability is rooted in insufficient scanline validation in libvips/iofuncs/image.c, specifically in the vips_image_sanity function, where scanline calculations can overflow an int. This overflow leads to incorrect buffer-region calculations that allow reads and writes to negative offsets in mmap-resident memory allocations. An attacker can craft a malicious TIFF file and supply it to an application using libvips; exploitation requires the application to process the file through the TIFF loader. The impact includes unauthorized access to adjacent image data in memory (data disclosure via uncompressed .v output) and process crashes; RCE has not been demonstrated but cannot be excluded. The fix, available in version 8.18.3, adds validation to ensure scanlines fit within INT_MAX bounds.
Affected products
- libvips libvips before 8.18.3
Timeline
- 2026-08-20: disclosed
- 2026-04-26: patched