Quick answers
- Is CVE-2026-33327 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33327 being exploited in the wild.
- How severe is CVE-2026-33327?
- Informational severity, with a CVSS score of 7, published 20 July 2026.
- Which products and versions are affected?
- Libvips <= 8.18.0.
- Is there a fix for CVE-2026-33327?
- A patch was published on 2026-03-07: 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-33327 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-33327?
- 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 the `vipsload` operation of libvips versions up to and including 8.18.0. The root cause is an incorrect calculation of image dimensions, which can trigger a heap-based buffer overflow during image processing. An attacker with local access could exploit this by providing a specially crafted image file to be processed by the library. Successful exploitation could lead to arbitrary code execution or a denial-of-service (DoS) condition. The issue has been addressed in version 8.18.1, and workarounds include blocking the 'VipsForeignLoadVips' operation or setting the VIPS_BLOCK_UNTRUSTED environment variable.
Affected products
- libvips libvips <= 8.18.0
Timeline
- 2026-03-07: patched: Fix merged into 8.18 branch
- 2026-07-17: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: CVE published to NVD