Quick answers
- Is CVE-2026-35590 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35590 being exploited in the wild.
- How severe is CVE-2026-35590?
- Informational severity, with a CVSS score of 6.8, published 20 July 2026.
- Which products and versions are affected?
- Libvips <= 8.18.1.
- Is there a fix for CVE-2026-35590?
- A patch was published on 2026-03-26: Fix merged into 8.18 branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35590 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-35590?
- 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 vulnerability exists in the EXIF decoder of libvips due to insufficient range validation of EXIF tag groups (ifdN) before passing data to libexif. This lack of validation can lead to a null pointer dereference or a heap-based buffer overflow when processing specially crafted EXIF metadata. An attacker with local access could exploit this to cause a denial-of-service (crash) of the application using the library. The issue is addressed in libvips version 8.18.2 by adding proper range checks in the exif.c component.
Affected products
- libvips libvips <= 8.18.1
Timeline
- 2026-03-26: patched: Fix merged into 8.18 branch
- 2026-07-17: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: CVE published to NVD