CVE-2025-64896
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCreative Cloud Desktop versions 6.4.0.361 and earlier are affected by a Creation of Temporary File in Directory with Incorrect Permissions vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to disrupt the application's functionality by manipulating temporary files. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAdobe Creative Cloud Desktop creates temporary files with insecure permissions in a known directory. An attacker can place or manipulate these temporary files by enticing a user to open a malicious file, causing the application to crash or become unresponsive, leading to denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.8.0.821CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Creative Cloud Desktop is installedCheck for the presence of Adobe Creative Cloud Desktop application in the system (e.g., look in Programs and Features, or check for the Creative Cloud Desktop executable)Affected if The application is not found on the system, this CVE does not apply
-
Identify the installed version of Adobe Creative Cloud DesktopLocate the version information for Adobe Creative Cloud Desktop (typically accessible via the application's About section, in installed program details, or via command-line tools that query installed software)Affected if Unable to determine the installed version, cannot assess exposure
-
Compare the installed version against the affected rangeCompare the discovered version number to the affected range: versions prior to 6.8.0.821 are vulnerableAffected if Installed version is less than 6.8.0.821 (e.g., 6.4.0.361, 6.5.0.0, 6.7.0.100, etc.)
-
Confirm temporary file behavior (if accessible)Observe whether Adobe Creative Cloud Desktop creates temporary files during file operations and check if those files are placed in a location accessible to other users (the vulnerability involves insecure permissions on temp files in a known directory)Affected if Temporary files are created with overly permissive access controls in a predictable location
A user is affected if Adobe Creative Cloud Desktop is installed with a version lower than 6.8.0.821 and the application handles files in a way that creates accessible temporary files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.8.0.821
Update Adobe Creative Cloud Desktop to a version newer than 6.4.0.361 to receive the vendor patch for this vulnerability.
Creative Cloud Desktop 6.8.0.821 or later
- 1. Open Adobe Creative Cloud Desktop application
- 2. Navigate to the settings or preferences menu
- 3. Check for available updates or manually trigger an update check
- 4. If automatic updates are enabled, the application should update to the latest version automatically
- 5. Alternatively, download Creative Cloud Desktop version 6.8.0.821 or later from the official Adobe website (helpx.adobe.com)
- 6. Restart the Creative Cloud Desktop application after updating
- 7. Verify the updated version by checking About/Version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64896 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data