dbcve.org
LibtiffApplication

CVE-2025-61145

MEDIUM · 5.0 CVSS v3.1 Published 2026-02-23
Fix available
A fix is available. Upgrade to 4.7.1 or later.
See remediation →
50/100
Remediation priority · Moderate
Public exploit

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
libtiff up to v4.7.1 was discovered to contain a double free via the component tools/tiffcrop.c.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-415

The same block of memory is freed twice, corrupting the allocator's bookkeeping in ways an attacker can shape toward code execution. It usually stems from tangled ownership of a pointer. The fix is clear, single ownership of each allocation and clearing pointers once they are freed.

General guidance for the double free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibtiffApplication
Affected:< 4.7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.7.1 or later
Fixed in 4.7.1
Recommended fix High confidence

Libtiff 4.7.1 or later

  1. 1. Check your current libtiff version using 'tiffinfo -version' or by querying your system's package manager (e.g., 'dpkg -l | grep libtiff' or 'rpm -qa | grep tiff')
  2. 2. Identify the package manager or installation method used for libtiff in your environment (system package, source compilation, or bundled dependency)
  3. 3. For system-installed packages: use your OS package manager to upgrade (e.g., 'apt-get update && apt-get install libtiff' on Debian/Ubuntu, 'yum update libtiff' on RHEL/CentOS, or 'brew upgrade libtiff' on macOS)
  4. 4. For source-built installations: download libtiff 4.7.1 or later from the official source (gitlab.com/libtiff/libtiff/releases) and rebuild
  5. 5. If libtiff is bundled within another application: upgrade the parent application to a version that includes libtiff >= 4.7.1
  6. 6. Verify the fix by confirming the new version after upgrade (e.g., 'tiffinfo -version' should show 4.7.1 or higher)
Caveat Minor: As a point release upgrade, API/ABI compatibility is maintained; however, recompilation of applications linking against libtiff is recommended to ensure they use the new library

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61145 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data