tiffcrop overruns the stack in readSeparateStripsIntoBuffer
libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.
- Advisory
- CVE-2025-61144
- Library
- libtiff, tiff on Debian
- Published
- Severity
- 7.3 out of 10, as published
- Affected
- libtiff up to 4.7.1
- Fixed in
- see the upstream record
- Reaches you
- through a command-line tool
What triggers it
Running the tiffcrop command-line tool on a crafted TIFF.
What sillybos does
Not reached by opening a file
Opening or reading a file never reaches this flaw, so a check before decoding has nothing to refuse. Listed so that nobody expects it to.
readSeparateStripsIntoBuffer is tiffcrop's, in tools/; no library call opening a file runs it.
Proposed from the advisory's text on 2026-11-01, as part of folding the backfill into the record; confirmed by a person on 2026-11-03.
How to protect yourself
In general. Upgrade libtiff to a version that has the fix; the upstream record names it.
Specifically. Not a pre-decode matter: a command-line tool, not the library, runs the flawed code.
The general advice applies to every row here.
Sources
- https://osv.dev/vulnerability/DEBIAN-CVE-2025-61144
- The record entry, triaged 2026-11-03, last checked 2026-11-03