Skip to content
Fencer Vulns
critical 9.8

CVE-2016-9539 json

tools/tiffcrop.c in libtiff 4.0.6 has an out-of-bounds read in readContigTilesIntoBuffer().

published 2016-11-22 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10345

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

tools/tiffcrop.c in libtiff 4.0.6 has an out-of-bounds read in readContigTilesIntoBuffer(). Reported as MSVR 35092.

Patch / fix

  • tiff Debian 14, Debian 13, Debian 12 4.0.7-1

debian advisories DEBIAN-CVE-2016-9539

  • tiff Ubuntu 14.04 LTS 4.0.3-7ubuntu0.6
  • tiff Ubuntu 16.04 LTS 4.0.6-1ubuntu0.1

ubuntu advisories UBUNTU-CVE-2016-9539

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libtiff Arch Linux 4.0.7-1
  • lib32-libtiff Arch Linux 4.0.7-1

arch linux advisories AVG-85AVG-86

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-9539 updated cvss 3.3

libtiff: Out-of-bounds read in readContigTilesIntoBuffer()

  • Red Hat Enterprise Linux 5 libtiff Red Hat Enterprise Linux 6 libtiff Red Hat Enterprise Linux 7 libtiff, libtiff-tools, compat-libtiff3
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.33% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
  • CWE-125 Out-of-bounds Read

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.