Critical Security Flaw in libtiff: Arbitrary Code Execution Risk

libtiff Updated 01 May 2026

Summary

01/05/2026
N/A
Yes i
High
7.8

RLSA-2026:12265: Important: libtiff security update. Affects libtiff versions < 0:4.6.0-6.el10_1.3. Fixed in 0:4.6.0-6.el10_1.3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libtiff is a widely used library for manipulating Tagged Image File Format (TIFF) files, which are commonly utilized in various applications for image storage and processing. The library provides essential functions for reading and writing TIFF files, making it a crucial component in many software systems that handle image data. However, recent findings have revealed a significant vulnerability that could allow attackers to exploit the library, leading to severe security implications.

Vulnerability Detail

The vulnerability, identified as CVE-2026-4775, stems from a signed integer overflow during TIFF file processing. This flaw can be exploited to execute arbitrary code or cause a denial of service, potentially compromising the integrity and availability of affected systems. The issue arises when the library processes specially crafted TIFF files, which can manipulate memory allocation and execution flow, leading to unauthorized actions.

How To Fix

Minimum fixed version

0:4.6.0-6.el10_1.3

This is the first release that contains the fix.

sudo dnf update libtiff

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users are advised to avoid processing untrusted TIFF files until the package is updated. Implementing strict file validation and sanitization can also help mitigate the risk of exploitation.

Conclusion

The libtiff library is critical for handling TIFF files, but the recently discovered CVE-2026-4775 vulnerability poses significant risks. Users are strongly encouraged to update their libtiff packages to the latest secure version to protect their systems from potential exploitation. Utilizing tools like Vulert can further enhance security by monitoring for vulnerabilities.

See every vulnerability recorded for libtiff →

Share this vulnerability

FAQ

CVE-2026-4775 is a security vulnerability in the libtiff library that allows for arbitrary code execution or denial of service due to a signed integer overflow in TIFF file processing.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your manifest file.

Exploitation of this vulnerability can lead to unauthorized code execution, potentially allowing attackers to gain control over affected systems or disrupt service availability.

Yes, a patch is available. Users should update to libtiff version 0:4.6.0-6.el10_1.3 or later to mitigate the risk associated with this vulnerability.

If an immediate update is not possible, avoid processing untrusted TIFF files and implement strict validation and sanitization measures to reduce the risk of exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for libtiff.

How To Fix

Minimum fixed version

0:4.6.0-6.el10_1.3

This is the first release that contains the fix.

sudo dnf update libtiff

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.