CVE-2025-61144: Buffer Overflow
Published Feb 23, 2026
·Updated
libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.
Affected Software
4 affected componentsFixes available
libtiff<=4.7.1
LibTIFF libtiff<4.7.1
Microsoft cbl2 libtiff 4.6.0-11
Microsoft azl3 libtiff 4.6.0-11
Remediation
Event History
Feb 23, 2026
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·07:22 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 26, 2026
Data Sourced
via Microsoft·09:01 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·09:01 AM
Affected Software
Updated
via Microsoft·09:01 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-61144?
CVE-2025-61144 is classified as a high severity vulnerability due to its potential to cause a stack overflow.
2
How do I fix CVE-2025-61144?
To mitigate CVE-2025-61144, upgrade libtiff to version 4.7.2 or later, which contains the necessary patches.
3
What software versions are affected by CVE-2025-61144?
CVE-2025-61144 affects libtiff versions up to and including 4.7.1.
4
What specific function is vulnerable in CVE-2025-61144?
The vulnerable function in CVE-2025-61144 is readSeparateStripsIntoBuffer.
5
How can CVE-2025-61144 impact my system?
CVE-2025-61144 can lead to a stack overflow, potentially allowing an attacker to execute arbitrary code on the affected system.