CVE-2025-61144
Libtiff buffer overflow
- Published23 Feb 2026
Description
libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://gist.github.com/optionGo/5ad17e96a0a40f03578dd6c9f8645952
- https://gitlab.com/libtiff/libtiff/-/commit/09f53a86cf26dfd961925227e59e180db617f26d
- https://gitlab.com/libtiff/libtiff/-/commit/88cf9dbb48f6e172629795ecffae35d5052f68aa
- https://gitlab.com/libtiff/libtiff/-/issues/740
- https://gitlab.com/libtiff/libtiff/-/merge_requests/757
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-61144 being actively exploited?
CVE-2025-61144 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.26%.
How severe is CVE-2025-61144?
CVE-2025-61144 has a CVSS 3.1 base score of 7.3, rated high. EPSS estimates a 0.26% probability of exploitation.
Which products are affected by CVE-2025-61144?
Affected products include Libtiff.
How do I fix CVE-2025-61144?
Upgrade affected software to a fixed version, for example Libtiff 4.7.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-61144 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.