CVE-2026-4775
Libtiff: libtiff: arbitrary code execution or denial of service via signed integer overflow in tiff file processing
CVE-2026-4775 is fixed in 15 products on 1 platform, first by RHSA-2026:19586, released March 24, 2026. It is not reported as exploited. Patch Radar priority: High.
High
CVSS
7.8
Important
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0057
47th percentile
A flaw was found in the libtiff library. A remote attacker could exploit a signed integer overflow vulnerability in the putcontig8bitYCbCr44tile function by providing a specially crafted TIFF file. This flaw can lead to an out-of-bounds heap write due to incorrect memory pointer calculations, potentially causing a denial of service (application crash) or arbitrary code execution.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| compat-libtiff3 · RHEL 8 | 0:3.9.4-15.el8_10 | RHSA-2026:20585 | May 27, 2026 |
| compat-libtiff3 · almalinux 8 | 3.9.4-15.el8_10 | ALSA-2026:20585 | May 26, 2026 |
| compat-libtiff3 · ol 8 | 0:3.9.4-15.el8_10 | ELSA-2026-20585 | May 26, 2026 |
| compat-libtiff3 · rocky 8 | 0:3.9.4-15.el8_10 | RLSA-2026:20585 | May 29, 2026 |
| libtiff · RHEL 10 | 4.6.0-6.el10_0.3 | RHSA-2026:19586 | Mar 24, 2026 |
| libtiff · RHEL 8 | 0:4.0.9-37.el8_10 | RHSA-2026:16055 | May 15, 2026 |
| libtiff · RHEL 9 | 0:4.4.0-18.el9_8 | RHSA-2026:19363 | Apr 30, 2026 |
| libtiff · almalinux 10 | 4.6.0-8.el10_2.1 | ALSA-2026:19150 | May 19, 2026 |
| libtiff · almalinux 8 | 4.0.9-37.el8_10 | ALSA-2026:16055 | May 11, 2026 |
| libtiff · almalinux 9 | 4.4.0-18.el9_8 | ALSA-2026:19363 | May 19, 2026 |
| libtiff · amzn 2023 | 4.4.0-4.amzn2023.0.26 | ALAS2023-2026-1547 | Apr 13, 2026 |
| libtiff · ol 10 | 0:4.6.0-6.el10_1.3 | ELSA-2026-12265 | Apr 30, 2026 |
| libtiff · ol 8 | 0:4.0.9-37.el8_10 | ELSA-2026-16055 | May 11, 2026 |
| libtiff · ol 9 | 0:4.4.0-15.el9_7.3 | ELSA-2026-12271 | Apr 30, 2026 |
| libtiff · rocky 10 | 0:4.6.0-8.el10_2.1 | RLSA-2026:19150 | May 29, 2026 |
| libtiff · rocky 8 | 0:4.0.9-37.el8_10 | RLSA-2026:16055 | May 13, 2026 |
| libtiff · rocky 9 | 0:4.4.0-18.el9_8 | RLSA-2026:19363 | May 28, 2026 |
| libtiff-debuginfo · amzn 2023 | 4.4.0-4.amzn2023.0.26 | ALAS2023-2026-1547 | Apr 13, 2026 |
| libtiff-debugsource · amzn 2023 | 4.4.0-4.amzn2023.0.26 | ALAS2023-2026-1547 | Apr 13, 2026 |
| libtiff-devel · RHEL 8 | 0:4.0.9-37.el8_10 | RHSA-2026:16055 | May 15, 2026 |
| libtiff-devel · RHEL 9 | 0:4.4.0-18.el9_8 | RHSA-2026:19363 | Apr 30, 2026 |
| libtiff-devel · almalinux 10 | 4.6.0-8.el10_2.1 | ALSA-2026:19150 | May 19, 2026 |
| libtiff-devel · almalinux 8 | 4.0.9-37.el8_10 | ALSA-2026:16055 | May 11, 2026 |
| libtiff-devel · almalinux 9 | 4.4.0-18.el9_8 | ALSA-2026:19363 | May 19, 2026 |
| libtiff-devel · amzn 2023 | 4.4.0-4.amzn2023.0.26 | ALAS2023-2026-1547 | Apr 13, 2026 |
| libtiff-devel · ol 10 | 0:4.6.0-6.el10_1.3 | ELSA-2026-12265 | Apr 30, 2026 |
| libtiff-devel · ol 8 | 0:4.0.9-37.el8_10 | ELSA-2026-16055 | May 11, 2026 |
| libtiff-devel · ol 9 | 0:4.4.0-15.el9_7.3 | ELSA-2026-12271 | Apr 30, 2026 |
| libtiff-static · amzn 2023 | 4.4.0-4.amzn2023.0.26 | ALAS2023-2026-1547 | Apr 13, 2026 |
| libtiff-tools · RHEL 8 | 0:4.0.9-37.el8_10 | RHSA-2026:16055 | May 15, 2026 |
| libtiff-tools · RHEL 9 | 0:4.4.0-18.el9_8 | RHSA-2026:19363 | Apr 30, 2026 |
| libtiff-tools · almalinux 10 | 4.6.0-8.el10_2.1 | ALSA-2026:19150 | May 19, 2026 |
| libtiff-tools · almalinux 8 | 4.0.9-37.el8_10 | ALSA-2026:16055 | May 11, 2026 |
| libtiff-tools · almalinux 9 | 4.4.0-18.el9_8 | ALSA-2026:19363 | May 19, 2026 |
| libtiff-tools · amzn 2023 | 4.4.0-4.amzn2023.0.26 | ALAS2023-2026-1547 | Apr 13, 2026 |
| libtiff-tools · ol 10 | 0:4.6.0-6.el10_1.3 | ELSA-2026-12265 | Apr 30, 2026 |
| libtiff-tools · ol 8 | 0:4.0.9-37.el8_10 | ELSA-2026-16055 | May 11, 2026 |
| libtiff-tools · ol 9 | 0:4.4.0-15.el9_7.3 | ELSA-2026-12271 | Apr 30, 2026 |
| libtiff-tools-debuginfo · amzn 2023 | 4.4.0-4.amzn2023.0.26 | ALAS2023-2026-1547 | Apr 13, 2026 |
| mingw-libtiff · rocky 8 | 0:4.0.9-4.el8_10 | RLSA-2026:14929 | May 11, 2026 |
| mingw32-libtiff · RHEL 8 | 0:4.0.9-4.el8_10 | RHSA-2026:14929 | May 15, 2026 |
| mingw32-libtiff · almalinux 8 | 4.0.9-4.el8_10 | ALSA-2026:14929 | May 7, 2026 |
| mingw32-libtiff · ol 8 | 0:4.0.9-4.el8_10 | ELSA-2026-14929 | May 8, 2026 |
| mingw32-libtiff-static · RHEL 8 | 0:4.0.9-4.el8_10 | RHSA-2026:14929 | May 15, 2026 |
| mingw32-libtiff-static · almalinux 8 | 4.0.9-4.el8_10 | ALSA-2026:14929 | May 7, 2026 |
| mingw32-libtiff-static · ol 8 | 0:4.0.9-4.el8_10 | ELSA-2026-14929 | May 8, 2026 |
| mingw64-libtiff · RHEL 8 | 0:4.0.9-4.el8_10 | RHSA-2026:14929 | May 15, 2026 |
| mingw64-libtiff · almalinux 8 | 4.0.9-4.el8_10 | ALSA-2026:14929 | May 7, 2026 |
| mingw64-libtiff · ol 8 | 0:4.0.9-4.el8_10 | ELSA-2026-14929 | May 8, 2026 |
| mingw64-libtiff-static · RHEL 8 | 0:4.0.9-4.el8_10 | RHSA-2026:14929 | May 15, 2026 |
| mingw64-libtiff-static · almalinux 8 | 4.0.9-4.el8_10 | ALSA-2026:14929 | May 7, 2026 |
| mingw64-libtiff-static · ol 8 | 0:4.0.9-4.el8_10 | ELSA-2026-14929 | May 8, 2026 |
| tiff · Debian 12.15 (bookworm) | 4.5.0-6+deb12u4 | DEBIAN-CVE-2026-4775 | Mar 24, 2026 |
| tiff · Debian 13.5 (trixie) | 4.7.0-3+deb13u2 | DEBIAN-CVE-2026-4775 | Mar 24, 2026 |
| tiff · Debian 14 | 4.7.1-2 | DEBIAN-CVE-2026-4775 | Mar 24, 2026 |
| tiff · opensuse-leap 16.0 | 4.7.2-160000.1.1 | OPENSUSE-SU-2026:21289-1 | Jul 10, 2026 |
| tiff · sles 15.6 | 4.7.2-150600.3.29.1 | SUSE-SU-2026:2853-1 | Jul 10, 2026 |
| tiff · sles 15.7 | 4.7.2-150600.3.29.1 | SUSE-SU-2026:2853-1 | Jul 10, 2026 |
| tiff · sles 16.0 | 4.7.2-160000.1.1 | SUSE-SU-2026:22616-1 | Jul 10, 2026 |
| tiff-man · opensuse-leap 16.0 | 4.7.2-160000.1.1 | OPENSUSE-SU-2026:21289-1 | Jul 10, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.