CVE-2025-8177VulnerabilityPublished 26 Jul 2025Updated 28 Jul 2025

CVE-2025-8177: LibTIFF · Buffer Overflow

Affects LibTIFFSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium · end of life, no fix coming : replace or isolate LibTIFF; no fix will be released.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

No fix will be released: LibTIFF is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

Product	Affected	Fixed in
GitHublibtiff/libtiff`pkg:github/libtiff/libtiff`Other threats	Affected =4.0 =4.1 =4.2 =4.3 =4.4 =4.5 =4.6 =4.7.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade LibTIFF to a supported and patched version beyond 4.7.0 where this vulnerability is resolved. Since the affected versions are unsupported, migrating to the latest stable release is critical. 2. Audit all internal systems and applications to identify usage of LibTIFF, especially legacy or custom-built software that may embed older versions. 3. Restrict local access to systems running vulnerable LibTIFF versions by enforcing strict access controls, including least privilege principles and multi-factor authentication for local logins. 4. Implement application whitelisting and endpoint protection to detect and prevent exploitation attempts involving buffer overflow behaviors. 5. Monitor system logs and behavior for unusual activity indicative of local exploitation attempts, such as crashes or unexpected process executions related to image processing tools. 6. Educate internal users about the risks of running outdated software and the importance of reporting anomalies. 7. If upgrading is not immediately feasible, consider isolating vulnerable systems within segmented network zones to limit potential lateral movement. 8. Regularly review and apply security patches for all third-party libraries and dependencies to prevent similar vulnerabilities.

Description

A vulnerability was found in LibTIFF up to 4.7.0. It has been rated as critical. This issue affects the function setrow of the file tools/thumbnail.c. The manipulation leads to buffer overflow. An attack has to be approached locally. The patch is named e8c9d6c616b19438695fd829e58ae4fde5bfbc22. It is recommended to apply a patch to fix this issue. This vulnerability only affects products that are no longer supported by the maintainer.

Impact

For European organizations, the impact of CVE-2025-8177 is moderate but context-dependent. Organizations relying on legacy or unsupported versions of LibTIFF in their internal image processing workflows, digital asset management systems, or custom applications may be at risk if local attackers gain access. The vulnerability could enable privilege escalation or local code execution, potentially leading to data corruption, service disruption, or lateral movement within internal networks. However, since exploitation requires local access and the affected versions are no longer supported, the risk is mitigated if organizations maintain up-to-date software and restrict local access. Industries with high reliance on image processing, such as media, publishing, scientific research, and certain manufacturing sectors, might face operational disruptions if vulnerable software is exploited. Additionally, organizations with weak internal access controls or those that allow untrusted users local access to systems could be more vulnerable. The absence of known exploits in the wild reduces immediate risk, but the presence of a patch indicates the vulnerability is credible and should be addressed to prevent future exploitation attempts.

Summary

CVE-2025-8177 is a buffer overflow vulnerability identified in LibTIFF versions up to 4.7.0, specifically affecting the 'setrow' function within the file tools/thumbnail.c. LibTIFF is a widely used open-source library for reading and writing TIFF (Tagged Image File Format) files, commonly integrated into various image processing tools and software. The vulnerability arises due to improper handling of buffer boundaries in the setrow function, which can lead to memory corruption when manipulated locally. Exploitation requires local access with at least low privileges (PR:L), and no user interaction is necessary. The vulnerability has a CVSS 4.0 base score of 4.8, categorized as medium severity, reflecting limited attack vector (local), low complexity, and partial impact on confidentiality, integrity, and availability. Notably, this vulnerability affects only unsupported versions of LibTIFF, meaning that actively maintained versions are not impacted. There are no known exploits in the wild, and the maintainer has released a patch (commit e8c9d6c616b19438695fd829e58ae4fde5bfbc22) to address the issue. The vulnerability does not require user interaction and does not affect the scope beyond the local system. Given the local attack vector, exploitation would typically require an attacker to have some form of access to the target system, such as through compromised credentials or physical access. The buffer overflow could potentially allow an attacker to execute arbitrary code or cause a denial of service by crashing the application using the vulnerable LibTIFF version. However, the impact is limited by the need for local access and the lack of remote exploitation capability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Aug 2025, 00:57 UTC

Technical details

References

Community reviews

Related threats