CVE-2025-61145: libtiff up to v4.7.1 was discovered to contain a double free via the component tools/tiffcrop.c.
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: tiff (Debian:14) 4.7.1-1; libtiff (Red Hat:hummingbird:1) 0:4.7.1-2.1.hum1; libtiff-devel (Red Hat:hummingbird:1) 0:4.7.1-2.1.hum1.
Low priority for now. Upgrade to tiff (Debian:14) 4.7.1-1; libtiff (Red Hat:hummingbird:1) 0:4.7.1-2.1.hum1; libtiff-devel (Red Hat:hummingbird:1) 0:4.7.1-2.1.hum1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Feb 23, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-415
Report tools
Action score
20
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libtiff | libtiff | cpe:2.3:a:libtiff:libtiff |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libtiff libtiffbefore 4.7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | tiff | from 0 | — |
| Debian:14 | tiff | before 4.7.1-1 | 4.7.1-1 |
| Red Hat:hummingbird:1 | libtiff | before 0:4.7.1-2.1.hum1 | 0:4.7.1-2.1.hum1 |
| Red Hat:hummingbird:1 | libtiff-devel | before 0:4.7.1-2.1.hum1 | 0:4.7.1-2.1.hum1 |
| Red Hat:hummingbird:1 | libtiff-static | before 0:4.7.1-2.1.hum1 | 0:4.7.1-2.1.hum1 |
| Red Hat:hummingbird:1 | libtiff-tools | before 0:4.7.1-2.1.hum1 | 0:4.7.1-2.1.hum1 |
Same product
libtiff: all recordsOther highest-scoring records for the same primary product.
- CVE-2006-3459Multiple stack-based buffer overflows in the TIFF library (libtiff) before 3.8.2, as used in Adobe Reader 9.3.0 and other products, allow…47Plan
- CVE-2004-1308Integer overflow in (1) tif_dirread.c and (2) tif_fax3.c for libtiff 3.5.7 and 3.7.0 allows remote attackers to execute arbitrary code via…44Plan
- CVE-2015-8668Heap-based buffer overflow in the PackBitsPreEncode function in tif_packbits.c in bmp2tiff in libtiff 4.0.6 and earlier allows remote…43Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-61143Feb 23, 2026 · libtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tif_open.c.22Monitor
- ← EarlierCVE-2025-61144Feb 23, 2026 · libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.29Monitor
- Later →CVE-2026-4775Mar 24, 2026 · Libtiff: libtiff: arbitrary code execution or denial of service via signed integer overflow in tiff file processing31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:tiff | 4.7.1-1 · Debian:14 | Package registry (OSV) |
| red hat:libtiff | 0:4.7.1-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libtiff-devel | 0:4.7.1-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libtiff-static | 0:4.7.1-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libtiff-tools | 0:4.7.1-2.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.