CVE-2026-70651 libvips CVE debrief

Who should care

Defenders responsible for systems handling image processing, especially those using libvips, should assess exposure and prioritize updating to version 8.18.3 or later. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review systems for potential exposure, monitor for crafted multi-page TIFF images, and plan for updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-70651 is a vulnerability in libvips that can cause a heap buffer over-read and process crash. Defenders should prioritize verifying and updating libvips, especially in image processing systems, and monitor for crafted TIFF images. The issue is fixed in version 8.18.3.

• Potential process crashes due to heap buffer over-read
• Need for verification of libvips version and exposure to crafted TIFF images
• Priority on updating libvips to version 8.18.3 or later
• Monitoring for crafted multi-page TIFF images

Technical summary

The vulnerability in libvips can cause a heap buffer over-read and process crash when loading a crafted multi-page TIFF image. This is due to flawed calculations in libvips/foreign/magick6load.c and libvips/foreign/magick7load.c that multiply the per-page Ysize by n_frames without a checked bound. The issue is fixed in version 8.18.3. The vulnerability has a CVSS score of 6.9 and is considered MEDIUM severity. Most package-manager builds include libtiff and do not use this affected fallback path. Affected systems handling image processing should assess exposure and prioritize updating to the fixed version.

Defensive priority

Defenders should prioritize verifying and updating libvips to version 8.18.3 or later, especially in systems handling image processing.

Recommended defensive actions

• Verify and update libvips to version 8.18.3 or later
• Review systems handling image processing for potential exposure
• Monitor for crafted multi-page TIFF images
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is caused by a heap buffer over-read in libvips/foreign/magick6load.c and libvips/foreign/magick7load.c. Most package-manager builds include libtiff and do not use this affected fallback path.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.