# CVE-2026-4775: Libtiff: libtiff: arbitrary code execution or denial of service via signed integer overflow in tiff file processing > Remote attackers can trigger arbitrary code execution or denial of service via a crafted TIFF file exploiting a signed integer overflow in libtiff. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 24 Mar 2026 - **Updated:** 2 Oct 2026 - **Also known as:** ALPINE-CVE-2026-4775, ALSA-2026:12265, ALSA-2026:12271, ALSA-2026:14929, ALSA-2026:16055, ALSA-2026:19150, ALSA-2026:19363, ALSA-2026:20585, AZL-80843, AZL-80919, BELL-CVE-2026-4775, CLSA-2026-1778090588, CLSA-2026-1778166747, CLSA-2026-1781100101, CLSA-2026-1783356013, DEBIAN-CVE-2026-4775, ECHO-2ccd-8b25-a651, GHSA-cm99-m826-vgg7, MGASA-2026-0114, MINI-76j3-7vpc-cf79, OESA-2026-1806, RHSA-2026:12265, RHSA-2026:12271, RHSA-2026:14929, RHSA-2026:16055, RHSA-2026:19150, RHSA-2026:19363, RHSA-2026:19585, RHSA-2026:19586, RHSA-2026:19604, RHSA-2026:19608, RHSA-2026:19609, RHSA-2026:19657, RHSA-2026:19659, RHSA-2026:19702, RHSA-2026:20583, RHSA-2026:20585, RHSA-2026:20591, RHSA-2026:20592, RHSA-2026:24992, RHSA-2026:25910, RHSA-2026:30349, RHSA-2026:33388, RLSA-2026:12265, RLSA-2026:12271, RLSA-2026:14929, RLSA-2026:16055, RLSA-2026:19150, RLSA-2026:19363, RLSA-2026:20585, ROOT-OS-ALPINE-320-CVE-2026-4775, SUSE-SU-2026:1965-1, SUSE-SU-2026:1966-1, SUSE-SU-2026:1967-1, SUSE-SU-2026:21675-1, SUSE-SU-2026:21685-1, UBUNTU-CVE-2026-4775, openSUSE-SU-2026:10650-1 ## What is CVE-2026-4775? CVE-2026-4775 is a high-severity vulnerability in Debian Debian Linux, published on 24 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2026-4775? It affects 13 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libtiff` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.3 | | `libtiff` | AlmaLinux:10 | All versions | 4.6.0-8.el10_2.1 | | `libtiff-devel` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.3 | | `libtiff-devel` | AlmaLinux:10 | All versions | 4.6.0-8.el10_2.1 | | `libtiff-tools` | AlmaLinux:10 | All versions | 4.6.0-6.el10_1.3 | | `libtiff-tools` | AlmaLinux:10 | All versions | 4.6.0-8.el10_2.1 | | `compat-libtiff3` | AlmaLinux:8 | All versions | 3.9.4-15.el8_10 | | `libtiff` | AlmaLinux:8 | All versions | 4.0.9-37.el8_10 | | `libtiff-devel` | AlmaLinux:8 | All versions | 4.0.9-37.el8_10 | | `libtiff-tools` | AlmaLinux:8 | All versions | 4.0.9-37.el8_10 | | `mingw32-libtiff` | AlmaLinux:8 | All versions | 4.0.9-4.el8_10 | | `mingw32-libtiff-static` | AlmaLinux:8 | All versions | 4.0.9-4.el8_10 | | `mingw64-libtiff` | AlmaLinux:8 | All versions | 4.0.9-4.el8_10 | | `mingw64-libtiff-static` | AlmaLinux:8 | All versions | 4.0.9-4.el8_10 | | `libtiff` | AlmaLinux:9 | All versions | 4.4.0-15.el9_7.3 | | `libtiff` | AlmaLinux:9 | All versions | 4.4.0-18.el9_8 | | `libtiff-devel` | AlmaLinux:9 | All versions | 4.4.0-15.el9_7.3 | | `libtiff-devel` | AlmaLinux:9 | All versions | 4.4.0-18.el9_8 | | `libtiff-tools` | AlmaLinux:9 | All versions | 4.4.0-15.el9_7.3 | | `libtiff-tools` | AlmaLinux:9 | All versions | 4.4.0-18.el9_8 | | `libtiff` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.3 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.3 | | `libtiff-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.3 | | `libtiff-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.3 | | `libtiff-tools` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.3 | | `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:4.6.0-6.el10_1.3 | | `libtiff` | Red Hat:enterprise_linux:10.2 | All versions | 0:4.6.0-8.el10_2.1 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:4.6.0-8.el10_2.1 | | `libtiff-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:4.6.0-8.el10_2.1 | | `libtiff-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:4.6.0-8.el10_2.1 | | `libtiff-tools` | Red Hat:enterprise_linux:10.2 | All versions | 0:4.6.0-8.el10_2.1 | | `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:4.6.0-8.el10_2.1 | | `compat-libtiff3` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-15.el8_10 | | `compat-libtiff3-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-15.el8_10 | | `compat-libtiff3-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-15.el8_10 | | `libtiff` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-37.el8_10 | | `libtiff-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-37.el8_10 | | `libtiff-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-37.el8_10 | | `libtiff-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-37.el8_10 | | `libtiff-tools-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-37.el8_10 | Products: Debian Debian Linux, Libtiff Libtiff, Redhat Ai Inference Server, Redhat Codeready Linux Builder, Redhat Codeready Linux Builder Eus, Redhat Enterprise Linux, Redhat Enterprise Linux Els, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Update Services for Sap Solutions, Redhat Hardened Images, Redhat Openshift Ai. ## How do I fix CVE-2026-4775? Apply the vendor's patch. ## Is CVE-2026-4775 being exploited? There is no known exploitation of CVE-2026-4775 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-4775 and fix it if it is affected. What it is: CVE-2026-4775 is a high-severity vulnerability in Debian Debian Linux, published on 24 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-4775 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-4775/ (Markdown: https://insights.sbomify.com/CVE-2026-4775/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4775 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4775 - OSV: https://osv.dev/vulnerability/CVE-2026-4775 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-4775/ Summaries are generated and may contain mistakes; the official description above is the record.