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.
https://github.com/libvips/libvips/releases/tag/v8.7.4
https://github.com/libvips/libvips/commit/00622428bda8d7521db8d74260b519fa41d69d0a
https://blog.silentsignal.eu/2019/04/18/drop-by-drop-bleeding-through-libvips/