Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-8331

libtiff: FAX IFD Entry Parsing Type Confusion

Overview

Published
28 Oct 2016
Modified
17 Jun 2026
High CVE
0 Registry packages
3 OS packages
4 Linux distributions
Yes Fix available

Description

An exploitable remote code execution vulnerability exists in the handling of TIFF images in LibTIFF version 4.0.6. A crafted TIFF document can lead to a type confusion vulnerability resulting in remote code execution. This vulnerability can be triggered via a TIFF file delivered to the application using LibTIFF's tag extension functionality.

Source: OX vulnerability database

Severity

8.1 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Red Hat 1 release · 1 package

wont fix 1
compat-libtiff3
Red Hat fixes for CVE-2016-8331
ReleasePackageFixed in
7 compat-libtiff3 wont fix

debian 4 releases · 1 package

fixed 4
tiff
debian fixes for CVE-2016-8331
ReleasePackageFixed in
11 tiff 4.0.6-3
12 tiff 4.0.6-3
13 tiff 4.0.6-3
14 tiff 4.0.6-3

echo 1 release · 1 package

fixed 1
tiff
echo fixes for CVE-2016-8331
ReleasePackageFixed in
tiff 4.0.6-3

root.io debian 3 releases · 1 package

fixed 3
rootio-tiff
root.io debian fixes for CVE-2016-8331
ReleasePackageFixed in
11 rootio-tiff 4.0.6-3
12 rootio-tiff 4.0.6-3
13 rootio-tiff 4.0.6-3

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.