CVE-2025-61145

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory published 2026-02-23. NVD baseline CVSS 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.0Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
5.0
EG Score
5.0(medium)
EG Risk
23(Track)
EG Risk 23/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity50% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

February 23, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

fix double-free and memory leak exposed by issue #721 (!753) · Merge requests · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/merge_requests/753
generic

Here may be a double free vulnerability in tiffcrop (#736) · Issues · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/issues/736
generic

CVE-2025-61145.txt · GitHub

https://gist.github.com/optionGo/062f109569196dbffd8ac12020b42289

Vendor Advisories for CVE-2025-61145(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibtiff-main-4.7.1-2.1.hum12026-04-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
tiff4.2.0-1 ... 4.7.2-1 (51 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
tiff4.5.0-6 ... 4.7.2-1 (23 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
tiff4.7.0-3 ... 4.7.2-1 (10 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
tiff4.7.0-3, 4.7.0-4, 4.7.0-54.7.1-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 15:42 UTCEPSS rescore
  2. 2026-09-18 19:50 UTCOSV refresh
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-16 14:07 UTCEPSS rescore
  6. 2026-09-15 03:10 UTCEPSS rescore
  7. 2026-09-13 16:46 UTCEPSS rescore
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-11 09:36 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-08-30 22:47 UTCOSV refresh
  17. 2026-08-30 19:16 UTCEPSS rescore
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-26 14:45 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-24 14:16 UTCEPSS rescore
  24. 2026-08-23 00:18 UTCEPSS rescore
  25. 2026-08-21 23:48 UTCEPSS rescore
Show 55 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:47 UTCEPSS rescore
  4. 2026-08-17 13:46 UTCEPSS rescore
  5. 2026-08-16 14:55 UTCEPSS rescore
  6. 2026-08-16 02:13 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-15 01:29 UTCEPSS rescore
  9. 2026-08-14 09:14 UTCEG score recompute
  10. 2026-08-14 09:14 UTCVendor advisory
  11. 2026-08-14 09:14 UTCGHSA enrichment
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-13 01:17 UTCEG score recompute
  14. 2026-08-13 01:17 UTCVendor advisory
  15. 2026-08-13 01:17 UTCGHSA enrichment
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 13:42 UTCEPSS rescore
  18. 2026-08-11 06:53 UTCEG score recompute
  19. 2026-08-11 06:53 UTCVendor advisory
  20. 2026-08-11 06:53 UTCGHSA enrichment
  21. 2026-08-10 23:59 UTCEPSS rescore
  22. 2026-08-10 09:13 UTCEG score recompute
  23. 2026-08-10 09:13 UTCVendor advisory
  24. 2026-08-10 09:13 UTCGHSA enrichment
  25. 2026-08-09 13:46 UTCEPSS rescore
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-09 08:51 UTCEG score recompute
  28. 2026-08-09 08:51 UTCVendor advisory
  29. 2026-08-09 08:51 UTCGHSA enrichment
  30. 2026-08-08 16:36 UTCEPSS rescore
  31. 2026-08-07 21:00 UTCEG score recompute
  32. 2026-08-07 21:00 UTCVendor advisory
  33. 2026-08-07 21:00 UTCGHSA enrichment
  34. 2026-08-07 16:26 UTCEPSS rescore
  35. 2026-08-06 13:46 UTCEPSS rescore
  36. 2026-08-06 03:12 UTCEG score recompute
  37. 2026-08-06 03:12 UTCVendor advisory
  38. 2026-08-06 03:12 UTCGHSA enrichment
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-04 15:09 UTCEPSS rescore
  42. 2026-08-04 10:37 UTCEPSS rescore
  43. 2026-08-03 10:35 UTCEPSS rescore
  44. 2026-08-02 19:48 UTCEG score recompute▼ 0.50
  45. 2026-08-02 19:48 UTCVendor advisory
  46. 2026-08-02 19:48 UTCGHSA enrichment
  47. 2026-08-02 02:26 UTCEPSS rescore
  48. 2026-08-01 04:15 UTCEPSS rescore
  49. 2026-07-30 16:27 UTCEPSS rescore
  50. 2026-07-30 01:30 UTCEPSS rescore
  51. 2026-07-28 15:35 UTCEPSS rescore
  52. 2026-07-27 14:12 UTCEPSS rescore
  53. 2026-07-27 12:55 UTCEG score recompute
  54. 2026-07-27 12:55 UTCVendor advisory
  55. 2026-07-27 12:55 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2025-61145?
CVE-2025-61145 is a medium vulnerability published on February 23, 2026. libtiff up to v4.7.1 was discovered to contain a double free via the component tools/tiffcrop.c.
When was CVE-2025-61145 disclosed?
CVE-2025-61145 was first published in the National Vulnerability Database on February 23, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-61145 actively exploited?
CVE-2025-61145 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2025-61145?
CVE-2025-61145 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2025-61145?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-61145, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-61145

Explore →

Is Your Infrastructure Affected by CVE-2025-61145?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs