VulnerabilityPublished 9 Dec 2025

CVE-2025-64896: Adobe Creative Cloud Desktop · Creation of Temporary File in Directory with Incorrect Permissions

Affects Adobe Creative Cloud DesktopSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.5Medium

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

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

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

Attack Vector: Local: The vulnerable component 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 remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 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 or the CVSS exploit maturity 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
Adobe Creative Cloud Desktop	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-64896, organizations should implement the following specific measures: 1) Monitor Adobe's official channels for patches or updates addressing this vulnerability and apply them promptly once available. 2) Enforce strict file system permissions on directories used by Adobe Creative Cloud Desktop to store temporary files, ensuring that only authorized users and processes have write access. 3) Educate users about the risks of opening files from untrusted or unknown sources to reduce the likelihood of triggering the vulnerability via malicious files. 4) Employ endpoint protection solutions capable of detecting and blocking suspicious file manipulations or anomalous application behavior related to temporary file handling. 5) Consider application whitelisting or sandboxing techniques to limit the impact of potential exploitation. 6) Regularly audit and review user permissions and system configurations to prevent privilege escalation or unauthorized file access. 7) Implement network segmentation to isolate critical creative workstations, minimizing lateral movement if exploitation occurs. These targeted actions go beyond generic advice by focusing on controlling file permissions, user behavior, and system configurations specific to the vulnerability's exploitation vector.

Description

CVE-2025-64896 is a medium severity vulnerability in Adobe Creative Cloud Desktop versions 6.4.0.361 and earlier, involving the creation of temporary files in directories with incorrect permissions (CWE-379). This flaw can be exploited by an attacker to cause a denial-of-service (DoS) condition by manipulating these temporary files, disrupting application functionality. Exploitation requires user interaction, specifically opening a malicious file. The vulnerability does not impact confidentiality or integrity but affects availability. No known exploits are currently reported in the wild. Organizations using affected Adobe Creative Cloud Desktop versions should prioritize patching once available and implement strict file permission policies to mitigate risk. European countries with high usage of Adobe Creative Cloud, especially in creative industries, are more likely to be impacted.

Impact

For European organizations, the primary impact of CVE-2025-64896 is the potential denial-of-service of Adobe Creative Cloud Desktop, which could disrupt creative workflows, project timelines, and collaboration efforts. Industries such as media, advertising, design, and digital content creation, which heavily rely on Adobe Creative Cloud tools, may experience operational downtime or degraded performance. Although the vulnerability does not compromise data confidentiality or integrity, the availability impact can lead to significant productivity losses and potential financial consequences. Additionally, organizations with strict compliance requirements around operational continuity may face challenges if this vulnerability is exploited. The requirement for user interaction limits the attack surface but does not eliminate risk, especially in environments where users frequently handle files from external or untrusted sources. The absence of known exploits reduces immediate threat but does not preclude future exploitation, making proactive mitigation critical.

Summary

CVE-2025-64896 is a vulnerability identified in Adobe Creative Cloud Desktop versions 6.4.0.361 and earlier, classified under CWE-379, which concerns the creation of temporary files in directories with incorrect permissions. This security weakness allows an attacker to exploit the application by manipulating temporary files that the software creates during its operation. Because these temporary files are stored with improper permissions, an attacker with local access or through a crafted malicious file can interfere with the application's normal functioning, potentially causing a denial-of-service (DoS) condition. The attack vector requires user interaction, meaning the victim must open a malicious file to trigger the vulnerability. The CVSS v3.1 base score is 5.5, indicating a medium severity level, with the vector string AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, which translates to local attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality or integrity impact, but high impact on availability. There are no known exploits in the wild at the time of publication, and no patches have been linked yet. The vulnerability primarily affects the availability of the Adobe Creative Cloud Desktop application, potentially disrupting workflows that depend on it. Given Adobe Creative Cloud's widespread use in creative and design sectors, this vulnerability could impact productivity and operational continuity if exploited.

CWE-379Creation of Temporary File in Directory with Insecure Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.
Requirements
Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
Implementation
Try to store sensitive tempfiles in a directory which is not world readable -- i.e., per-user directories.
Implementation
Avoid using vulnerable temp file functions.
OWASP Cheat Sheets
Authorization (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

helpx.adobe.com/security/products/creative-cloud/apsb25-120.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Dec 2025, 21:11 UTC

WeaknessesCWE-379

Technical details

References

Community reviews

Related threats