CVE-2025-61144: libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.
Noroxi assessment
Priority: Monitor (action score 29/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.30% (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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: azl3 libtiff 4.6.0-11 on Azure Linux 3.0 4.6.0-12; cbl2 libtiff 4.6.0-11 on CBL Mariner 2.0 4.6.0-12.
Low priority for now. Upgrade to azl3 libtiff 4.6.0-11 on Azure Linux 3.0 4.6.0-12; cbl2 libtiff 4.6.0-11 on CBL Mariner 2.0 4.6.0-12 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.3% · 23th percentile
- CWE
- CWE-119
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
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 |
| SUSE:Linux Enterprise Micro 5.3 | tiff | before 4.0.9-150000.45.63.1 | 4.0.9-150000.45.63.1 |
| SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | tiff | before 4.0.9-44.109.1 | 4.0.9-44.109.1 |
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-9165Aug 19, 2025 · LibTIFF tiffcmp tiffcmp.c InitCCITTFax3 memory leak4Monitor
- ← 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
- Later →CVE-2025-61145Feb 23, 2026 · libtiff up to v4.7.1 was discovered to contain a double free via the component tools/tiffcrop.c.20Monitor
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 |
|---|---|---|
| azl3 libtiff 4.6.0-11 on Azure Linux 3.0 | 4.6.0-12 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 libtiff 4.6.0-11 on CBL Mariner 2.0 | 4.6.0-12 · CBL-Mariner Releases | Microsoft (MSRC) |
| 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) |
| suse:tiff | 4.0.9-44.109.1 · SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-8851196 days apartLibTIFF tiffcrop tiffcrop.c readSeparateStripsetoBuffer stack-based overflow19Monitor
- CVE-2025-8177212 days apartLibTIFF thumbnail.c setrow buffer overflow19Monitor
- CVE-2025-8961193 days apartLibTIFF tiffcrop tiffcrop.c main memory corruption7Monitor
- CVE-2025-8176212 days apartLibTIFF tiffmedian.c get_histogram use after free7Monitor
Not on record for this CVE: EPSS history · researcher credit · 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.