CVE-2025-9165: LibTIFF tiffcmp tiffcmp.c InitCCITTFax3 memory leak
Noroxi assessment
Priority: Monitor (action score 4/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.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 libtiff 4.6.0-7 on Azure Linux 3.0 4.6.0-8; azl3 libtiff 4.6.0-8 on Azure Linux 3.0 4.6.0-8; cbl2 libtiff 4.6.0-6 on CBL Mariner 2.0 4.6.0-8.
Low priority for now. Upgrade to azl3 libtiff 4.6.0-7 on Azure Linux 3.0 4.6.0-8; azl3 libtiff 4.6.0-8 on Azure Linux 3.0 4.6.0-8; cbl2 libtiff 4.6.0-6 on CBL Mariner 2.0 4.6.0-8 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
A flaw has been found in LibTIFF 4.7.0. This affects the function _TIFFmallocExt/_TIFFCheckRealloc/TIFFHashSetNew/InitCCITTFax3 of the file tools/tiffcmp.c of the component tiffcmp. Executing manipulation can lead to memory leak. The attack is restricted to local execution. This attack is characterized by high complexity. It is indicated that the exploitability is difficult. The exploit has been published and may be used. There is ongoing doubt regarding the real existence of this vulnerability. This patch is called ed141286a37f6e5ddafb5069347ff5d587e7a4e0. It is best practice to apply a patch to resolve this issue. A researcher disputes the security impact of this issue, because "this is a memory leak on a command line tool that is about to exit anyway". In the reply the project maintainer declares this issue as "a simple 'bug' when leaving the command line tool and (...) not a security issue at all".
- Published
- Aug 19, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-401
Report tools
Action score
4
Monitor
Low priority for now.
- CVSS
- 4 / 40 · 1.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulDB
- 2.0
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 libtiff4.7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
n/a LibTIFF
- 4.7.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | tiff | before 4.7.1-r0 | 4.7.1-r0 |
| Debian:12 | tiff | from 0 | — |
| Debian:13 | tiff | before 4.7.0-3+deb13u1 | 4.7.0-3+deb13u1 |
| Debian:14 | tiff | before 4.7.0-4 | 4.7.0-4 |
| openSUSE:Leap 15.6 | tiff | before 4.7.0-150600.3.18.1 | 4.7.0-150600.3.18.1 |
| openSUSE:Leap 16.0 | tiff | before 4.7.1-160000.1.1 | 4.7.1-160000.1.1 |
| openSUSE:Leap 16.0 | tiff-man | before 4.7.1-160000.1.1 | 4.7.1-160000.1.1 |
| openSUSE:Tumbleweed | tiff | before 4.7.0-8.1 | 4.7.0-8.1 |
| openSUSE:Tumbleweed | tkimg | before 2.1.0-1.1 | 2.1.0-1.1 |
| SUSE:Linux Enterprise Micro 5.3 | tiff | before 4.0.9-150000.45.55.1 | 4.0.9-150000.45.55.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | tiff | before 4.7.0-150600.3.18.1 | 4.7.0-150600.3.18.1 |
| SUSE:Linux Enterprise Server 16.0 | tiff | before 4.7.1-160000.1.1 | 4.7.1-160000.1.1 |
| SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | tiff | before 4.0.9-44.94.1 | 4.0.9-44.94.1 |
| SUSE:Linux Micro 6.0 | tiff | before 4.7.1-1.1 | 4.7.1-1.1 |
| SUSE:Linux Micro 6.1 | tiff | before 4.7.1-slfo.1.1_1.1 | 4.7.1-slfo.1.1_1.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 co46Plan
- 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 a44Plan
- CVE-2018-12900Heap-based buffer overflow in the cpSeparateBufToContigBuf function in tiffcp.c in LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0beta7, 4.43Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-8851Aug 11, 2025 · LibTIFF tiffcrop tiffcrop.c readSeparateStripsetoBuffer stack-based overflow19Monitor
- ← EarlierCVE-2025-8961Aug 14, 2025 · LibTIFF tiffcrop tiffcrop.c main memory corruption7Monitor
- Later →CVE-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
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-7 on Azure Linux 3.0 | 4.6.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 libtiff 4.6.0-8 on Azure Linux 3.0 | 4.6.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 libtiff 4.6.0-6 on CBL Mariner 2.0 | 4.6.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 libtiff 4.6.0-8 on CBL Mariner 2.0 | 4.6.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| alpine:tiff | 4.7.1-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:tiff | 4.7.0-3+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:tiff | 4.7.0-150600.3.18.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:tiff-man | 4.7.1-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:tkimg | 2.1.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:tiff | 4.0.9-150000.45.55.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:tiff | 4.7.0-150600.3.18.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- HeureuxBuilding (VulDB User)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.