Skip to main content
VulnerabilityPublished Updated

CVE-2023-26966: libtiff

Affects libtiffSource CVE Database V5

0

Not known to be exploited.

Data as of 26 Oct 2026, 12:29 UTC

Severity
Medium

Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jun 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHublibtiff/libtiffpkg:github/libtiff/libtiffOther threatsAffected
  • =4.5.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A buffer overflow vulnerability exists in libtiff version 4.5.0 within the uv_encode() function. This occurs when libtiff processes a corrupted little-endian TIFF file and the output is specified as big-endian.

References

Community reviews

Loading reviews…