Quick answers
- Is CVE-2026-70653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-70653 being exploited in the wild.
- How severe is CVE-2026-70653?
- Informational severity, published 20 August 2026.
- Which products and versions are affected?
- Libvips before 8.18.3.
- Is there a fix for CVE-2026-70653?
- A patch was published on 2026-05-13: Fix merged 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-70653 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-70653?
- 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
The vulnerability is a heap buffer over-read in the old-style Radiance RLE decoder in libvips/foreign/radiance.c. When processing a repeat marker at the beginning of a scanline in the scanline_read_old function, the code reads from q[-1] before any prior pixel has been initialized, resulting in disclosure of 4 bytes of adjacent heap memory. The vulnerability requires only that a crafted Radiance image be loaded via VipsForeignLoadRad—no authentication or special conditions. An attacker can use this to leak adjacent heap data, most commonly other image data. The fix was implemented in version 8.18.3 by deprecating the old-style RLE decoder.
Affected products
- libvips libvips before 8.18.3
Timeline
- 2026-05-13: patched: Fix merged in version 8.18.3
- 2026-08-20: disclosed