Critical Security Flaw in libtiff: Arbitrary Code Execution Risk

libtiff Updated 13 May 2026

Summary

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

RLSA-2026:16055: Important: libtiff security update. Affects libtiff versions < 0:4.0.9-37.el8_10. Fixed in 0:4.0.9-37.el8_10. 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 Penetration testing for web, API and mobile 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, providing essential functions for image processing in various applications. Its robust capabilities make it a staple in software that handles image data. However, vulnerabilities in this library can lead to severe security risks, including arbitrary code execution and denial of service, particularly when processing malformed TIFF files.

Vulnerability Detail

The vulnerability identified as CVE-2026-4775 is a signed integer overflow in the processing of TIFF files within the libtiff library. This flaw can be exploited by attackers to execute arbitrary code on the affected system or cause a denial of service. The issue arises from improper handling of integer values during TIFF file processing, leading to potential memory corruption and unpredictable behavior in applications that utilize libtiff.

How To Fix

Minimum fixed version

0:4.0.9-37.el8_10

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 workaround, users can avoid processing untrusted TIFF files until the package is updated. Additionally, implementing strict input validation for TIFF files may help reduce the risk of exploitation.

Conclusion

The libtiff library has a critical vulnerability (CVE-2026-4775) that poses significant risks, including arbitrary code execution and denial of service. It is essential for users to update to the latest patched version to safeguard their systems. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

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 during TIFF file processing.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your application's manifest file, you can determine if it is affected by CVE-2026-4775.

Exploitation of this vulnerability can lead to arbitrary code execution, allowing attackers to take control of the affected system, or cause a denial of service, disrupting application functionality.

Yes, a patch is available. Users should update their libtiff package to version 0:4.0.9-37.el8_10 or later to address the vulnerability.

You can use Vulert's playground to check if your application is affected by vulnerabilities like CVE-2026-4775 without needing to sign up. It utilizes your manifest file for real-time monitoring.

Related vulnerabilities

Recent vulnerabilities recorded for libtiff.

How To Fix

Minimum fixed version

0:4.0.9-37.el8_10

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