Vulnerability Database · Debian · Package report

tiff: vulnerability history, versions and safety

tiff is a package in the Debian ecosystem. Vulert records 435 vulnerabilities for it across 51 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
435 vulnerabilities recorded U435
i
37 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 26 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on tiff i

Updated on 23 Oct 2026

Careful: 37 of the 435 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 435 vulnerabilities on record across 2026 years, 5 in the last year.

What to do: Plan around the 37 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 435 over 2026 years · 5 in the last year i
  • Latest disclosure 26 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 37 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for tiff, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
4.7.2-1 U3 No Details →
4.7.1-3 U5 No Details →
4.7.1-2 U5 No Details →
4.7.1-1 U16 No Details →
4.7.0-5 U16 No Details →
4.7.0-4 U26 No Details →
4.7.0-3 U36 No Details →
4.7.0-2 U36 No Details →
4.7.0-1 U36 No Details →
4.6.0-2 U37 No Details →
4.6.0-1 U37 No Details →
4.5.1-1 U37 No Details →
4.5.1+git230720-5 U37 No Details →
4.5.1+git230720-4 U37 No Details →
4.5.1+git230720-3 U37 No Details →
4.5.1+git230720-2 U37 No Details →
4.5.1+git230720-1 U37 No Details →
4.5.1~rc3-1 U37 No Details →
4.5.0-6 U37 No Details →
4.5.0-5 U37 No Details →
4.5.0-4 U37 No Details →
4.5.0-3 U37 No Details →
4.5.0-2 U37 No Details →
4.5.0-1 U37 No Details →
4.5.0~rc3+git221213-1 U37 No Details →
4.5.0~rc1-1 U37 No Details →
4.5.0~rc1+git221213-1 U37 No Details →
4.4.0-6 U37 No Details →
4.4.0-5 U37 No Details →
4.4.0-4 U37 No Details →
4.4.0-3 U37 No Details →
4.4.0-2 U37 No Details →
4.4.0-1 U37 No Details →
4.4.0~rc1-1 U37 No Details →
4.3.0-8 U37 No Details →
4.3.0-7 U37 No Details →
4.3.0-6 U37 No Details →
4.3.0-5 U37 No Details →
4.3.0-4 U37 No Details →
4.3.0-3 U37 No Details →
4.3.0-2 U37 No Details →
4.3.0-1 U37 No Details →
4.2.0-1 U118 No Details →
4.2.0-1+deb11u8 U5 No Details →
4.2.0-1+deb11u7 U9 No Details →
4.2.0-1+deb11u6 U37 No Details →
4.2.0-1+deb11u5 U54 No Details →
4.2.0-1+deb11u4 U61 No Details →
4.2.0-1+deb11u3 U76 No Details →
4.2.0-1+deb11u2 U109 No Details →
4.2.0-1+deb11u1 U109 No Details →

Newest 51 of 51 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 4
  • 2004 6
  • 2005 10
  • 2006 28
  • 2008 2
  • 2009 4
  • 2010 30
  • 2011 8
  • 2012 12
  • 2013 12
  • 2014 2
  • 2015 2
  • 2016 65
  • 2017 91
  • 2018 32
  • 2019 5
  • 2020 2
  • 2021 10
  • 2022 38
  • 2023 48
  • 2024 6
  • 2025 13
  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 435 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for tiff

The 5 most severe of 435 vulnerabilities recorded for this package

Search all 435 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 →

Questions

About tiff

Is tiff safe to use?

Vulert records 435 vulnerabilities for tiff in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 435 not yet rated. 37 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does tiff have?

435 vulnerabilities are recorded for tiff in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 435 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tiff vulnerabilities disclosed?

5 vulnerabilities were recorded for tiff in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of tiff are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor tiff for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tiff version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.