CVE-2025-61144

HIGHNVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-02-23. NVD baseline CVSS 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

A fix is available — apply it.

libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
48(Track)
EG Risk 48/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
Severity73% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

February 23, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

CVE-2025-61144.txt · GitHub

https://gist.github.com/optionGo/5ad17e96a0a40f03578dd6c9f8645952
generic

Merge branch 'tiffcrop-740' into 'master' (09f53a86) · Commits · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/commit/09f53a86cf26dfd961925227e59e180db617f26d
generic

tiffcrop: avoid buffer overflow (88cf9dbb) · Commits · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/commit/88cf9dbb48f6e172629795ecffae35d5052f68aa
generic

avoid buffer overflow in tiffcrop #740 (!757) · Merge requests · libtiff / libtiff · GitLab

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

A stack-based buffer overflow occurs in tiffcrop (#740) · Issues · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/issues/740

Vendor Advisories for CVE-2025-61144(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.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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-19 15:03 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 14:52 UTCEPSS rescore
  10. 2026-09-11 09:36 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-08-31 18:34 UTCOSV refresh
  19. 2026-08-30 19:16 UTCEPSS rescore
  20. 2026-08-30 01:21 UTCEPSS rescore
  21. 2026-08-28 21:40 UTCEPSS rescore
  22. 2026-08-27 14:24 UTCEPSS rescore
  23. 2026-08-26 14:45 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-24 14:16 UTCEPSS rescore
Show 66 more
  1. 2026-08-23 00:18 UTCEPSS rescore
  2. 2026-08-21 23:48 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:47 UTCEPSS rescore
  6. 2026-08-17 13:46 UTCEPSS rescore
  7. 2026-08-16 14:55 UTCEPSS rescore
  8. 2026-08-16 02:13 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-15 01:29 UTCEPSS rescore
  11. 2026-08-14 22:24 UTCVendor advisory
  12. 2026-08-14 22:24 UTCGHSA enrichment
  13. 2026-08-14 09:14 UTCEG score recompute
  14. 2026-08-14 09:14 UTCVendor advisory
  15. 2026-08-14 09:14 UTCGHSA enrichment
  16. 2026-08-13 21:59 UTCEPSS rescore
  17. 2026-08-13 01:17 UTCEG score recompute
  18. 2026-08-13 01:17 UTCVendor advisory
  19. 2026-08-13 01:17 UTCGHSA enrichment
  20. 2026-08-12 13:50 UTCEPSS rescore
  21. 2026-08-12 01:16 UTCEG score recompute
  22. 2026-08-12 01:16 UTCVendor advisory
  23. 2026-08-12 01:16 UTCGHSA enrichment
  24. 2026-08-11 13:42 UTCEPSS rescore
  25. 2026-08-11 06:44 UTCEG score recompute
  26. 2026-08-11 06:44 UTCVendor advisory
  27. 2026-08-11 06:44 UTCGHSA enrichment
  28. 2026-08-10 23:59 UTCEPSS rescore
  29. 2026-08-10 13:20 UTCVendor advisory
  30. 2026-08-10 13:20 UTCGHSA enrichment
  31. 2026-08-09 21:50 UTCEG score recompute
  32. 2026-08-09 21:50 UTCVendor advisory
  33. 2026-08-09 21:50 UTCGHSA enrichment
  34. 2026-08-09 13:46 UTCEPSS rescore
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 08:51 UTCEG score recompute
  37. 2026-08-09 08:51 UTCVendor advisory
  38. 2026-08-09 08:51 UTCGHSA enrichment
  39. 2026-08-08 16:36 UTCEPSS rescore
  40. 2026-08-08 09:58 UTCVendor advisory
  41. 2026-08-08 09:58 UTCGHSA enrichment
  42. 2026-08-07 21:00 UTCEG score recompute
  43. 2026-08-07 21:00 UTCVendor advisory
  44. 2026-08-07 21:00 UTCGHSA enrichment
  45. 2026-08-07 16:26 UTCEPSS rescore
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-06 03:12 UTCEG score recompute
  48. 2026-08-06 03:12 UTCVendor advisory
  49. 2026-08-06 03:12 UTCGHSA enrichment
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-04 15:09 UTCEPSS rescore
  53. 2026-08-04 10:37 UTCEPSS rescore
  54. 2026-08-03 10:35 UTCEPSS rescore
  55. 2026-08-02 19:48 UTCEG score recompute▼ 2.50
  56. 2026-08-02 19:48 UTCVendor advisory
  57. 2026-08-02 19:48 UTCGHSA enrichment
  58. 2026-08-02 02:26 UTCEPSS rescore
  59. 2026-08-01 04:15 UTCEPSS rescore
  60. 2026-07-30 16:27 UTCEPSS rescore
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-28 15:35 UTCEPSS rescore
  63. 2026-07-27 14:12 UTCEPSS rescore
  64. 2026-07-27 12:55 UTCEG score recompute
  65. 2026-07-27 12:55 UTCVendor advisory
  66. 2026-07-27 12:55 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-61144?
CVE-2025-61144 is a high vulnerability published on February 23, 2026. libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.
When was CVE-2025-61144 disclosed?
CVE-2025-61144 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-61144 actively exploited?
CVE-2025-61144 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 82.9% of all scored CVEs.
What is the CVSS score of CVE-2025-61144?
CVE-2025-61144 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2025-61144?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-61144, 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-61144

Explore →

Is Your Infrastructure Affected by CVE-2025-61144?

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

Start Free Scan →Browse All CVEs