Quick answers
- Is CVE-2026-70654 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-70654 being exploited in the wild.
- How severe is CVE-2026-70654?
- Informational severity, with a CVSS score of 8.6, published 20 August 2026.
- Which products and versions are affected?
- Libvips prior to 8.18.3.
- Is there a fix for CVE-2026-70654?
- A patch was published on 2026-05-13: Fixed in version 8.18.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-70654 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-70654?
- 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
A copy-paste error in the vips_source_read_to_memory function in libvips/iofuncs/source.c uses VIPS_MAX instead of VIPS_MIN when calculating the remaining read size for heap-allocated buffers. When processing uncompressed PPM images with custom source definitions, this allows up to 4032 bytes to be written beyond the allocated buffer boundary. The vulnerability requires both custom source definitions and untrusted PPM input. The issue is fixed in libvips 8.18.3 (patched May 13, 2026).
Affected products
- libvips libvips prior to 8.18.3
Timeline
- 2026-08-20: disclosed
- 2026-05-13: patched: Fixed in version 8.18.3