Updated libtiff packages fix security vulnerabilities

libtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tifopen.c. CVE-2025-61143 libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function. CVE-2025-61144...

OESA-2026-1441 libtiff security update

This provides support for the Tag Image File Format TIFF, a widely used format for storing image data. The latest version of the TIFF specification is available on-line in several different formats.And contains command-line programs for manipulating TIFF format image files using the libtiff...

libtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tif_open.c.

...

CVE-2025-61143

libtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tifopen.c...

CVE-2025-61143

libtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tifopen.c...

LibTIFF 安全漏洞

LibTIFF is an open-source library for reading and writing TIFF Tagged Image File Format files. This library includes some command-line tools for processing TIFF files. Versions of LibTIFF prior to v4.7.1 have security vulnerabilities, which stem from a null pointer dereferencing in the component...

PT-2026-21536

Name of the Vulnerable Software and Affected Versions libtiff versions up to 4.7.1 Description The software component libtiff, specifically through the tif open.c file, contains a flaw that allows for a NULL pointer dereference. This issue could potentially lead to unexpected behavior or denial o...

SUSE CVE-2017-16232

LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service memory consumption, as demonstrated by tifopen.c, tiflzw.c, and tifaux.c. NOTE: Third parties were unable to reproduce the issue...

DEBIAN-CVE-2017-16232

LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service memory consumption, as demonstrated by tifopen.c, tiflzw.c, and tifaux.c. NOTE: Third parties were unable to reproduce the issue...