How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- Attack vector: Local — a local account, shell or session on the host is needed.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: Required — someone has to click, open or visit something.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: High — total loss, or loss the attacker controls.
- Integrity impact: High — total loss, or loss the attacker controls.
- Availability impact: High — total loss, or loss the attacker controls.
Weakness class
CVE-2025-61144 is classified as CWE-119: Improper Restriction of Operations within Memory Buffer Bounds. A read or write is performed without confirming it stays inside the allocated buffer, corrupting adjacent memory.
Affected software
CVE-2025-61144 is recorded against 1 package.
Timeline and source
Published on 23 February 2026 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from NVD.
References
gist.github.com
gitlab.com
gitlab.com
gitlab.com
gitlab.com
Other advisories for this package
libtiff has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-119: Improper Restriction of Operations within Memory Buffer Bounds) in other software:
