CVE Tools
Track your stack

CVE-2026-4775

Libtiff: libtiff: arbitrary code execution or denial of service via signed integer overflow in tiff file processing

No known exploitation. EPSS puts it in the 48th percentile. Fixed versions are out.

CVSS 3.17.8HighEPSS percentile48th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products6 fixed builds listed below
Check it yourself

OpenVAS · 75 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.136782

Run the check

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Red Hat Enterprise Linux 10Fixed builds0:4.6.0-6.el10_1.3, 0:4.0.9-37.el8_10, 0:4.4.0-15.el9_7.3Stated by: CVE record
  • Red Hat Enterprise Linux 10.0 Extended Update SupportFixed builds0:4.6.0-6.el10_0.3Stated by: CVE record
  • Red Hat Enterprise Linux 7 Extended Lifecycle SupportFixed builds0:3.9.4-12.el7_9.2Stated by: CVE record
  • Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update SupportFixed builds0:4.0.9-18.el8_4.2Stated by: CVE record
  • Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-OnFixed builds0:4.0.9-18.el8_4.2Stated by: CVE record

Versions as the sources state them. 16 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS48th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

16 events over 225 days, from the signal feeds we watch.

  1. Patch availableworkaround available, record updated
  2. Patch availableworkaround available, record updated
  3. Workaround availablerecord updated
  4. Workaround availablerecord updated
  5. Workaround availablerecord updated
  6. OpenVAS check added

Affected products

And 24 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 29 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Ai Inference Server, not every advisory.