CVE-2025-8961VulnerabilityPublished 14 Aug 2025Updated 23 Aug 2025

CVE-2025-8961: LibTIFF · Memory Corruption

Affects LibTIFFSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

4.8Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

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

Threat metrics

Exploit Maturity: POC

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: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within 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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Aug 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 2026-10-26.

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

Affected software

Product	Affected	Fixed in
LibTIFF	Affected =4.7.0	Fixed in–

AI-suggested

To mitigate CVE-2025-8961, European organizations should: 1) Immediately identify and inventory all systems using LibTIFF version 4.7.0, particularly those exposing the tiffcrop utility. 3) Restrict local access to systems running tiffcrop to trusted users only, enforcing strict access controls and user permissions to prevent untrusted local users from executing the vulnerable code. 4) Monitor local system logs and application logs for unusual crashes or abnormal behavior related to TIFF processing tools. 5) Employ application whitelisting and endpoint protection to detect and block exploitation attempts or abnormal memory corruption behaviors. 6) Educate local users about the risks of executing untrusted TIFF files or image processing commands. 7) In environments where image processing is automated, validate and sanitize TIFF inputs before processing to reduce the risk of malformed files triggering the vulnerability. 8) Implement layered security controls to prevent initial local access by unauthorized users, such as strong authentication, endpoint hardening, and network segmentation.

Description

A weakness has been identified in LibTIFF 4.7.0. This affects the function main of the file tiffcrop.c of the component tiffcrop. Executing manipulation can lead to memory corruption. The attack can only be executed locally. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, the impact of CVE-2025-8961 depends largely on the deployment context of LibTIFF 4.7.0 and the tiffcrop utility. Organizations using image processing pipelines, digital asset management systems, or any software that incorporates LibTIFF 4.7.0 and exposes the tiffcrop tool to local users could face risks of local denial of service or potential privilege escalation if combined with other vulnerabilities. The local attack vector reduces the risk for typical enterprise environments where user access is tightly controlled, but environments with shared workstations, development systems, or image processing servers accessible by multiple users could be vulnerable. The memory corruption could cause application crashes leading to service disruption or data loss in workflows relying on TIFF image manipulation. Although no direct remote exploitation is possible, the public availability of exploit code increases the risk of insider threats or attackers who have already gained limited local access. European organizations in sectors such as media, publishing, healthcare (medical imaging), and manufacturing (CAD and imaging tools) that rely on TIFF image processing may be more exposed. The vulnerability does not appear to allow remote code execution or data exfiltration directly, so the confidentiality and integrity impacts are limited. However, disruption of image processing services or potential local privilege escalation could have operational consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Aug 2025, 00:35 UTC

Technical details

References

Community reviews

Related threats