AnimateApplication · Adobe

CVE-2025-61804

HIGH · 7.8 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 23.0.15 / 24.0.12 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Animate versions 23.0.13, 24.0.10 and earlier are affected by a Heap-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. 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 · moderate confidence

Adobe Animate versions 23.0.13, 24.0.10 and earlier contain a Heap-based Buffer Overflow vulnerability that allows arbitrary code execution when a user opens a malicious file. The attack requires user interaction (opening a malicious file), but executes in the context of the current user.

MitigationUpdate Adobe Animate to the latest patched version once available, and educate users to avoid opening untrusted or unexpected .an and .fla files.

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
AnimateApplication
Affected:>= 23.0.0, < 23.0.15>= 24.0.0, < 24.0.12

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Adobe Animate is installed
    Check for the presence of Animate.exe in typical installation directories such as C:\Program Files\Adobe\Adobe Animate 2023 or C:\Program Files\Adobe\Adobe Animate 2024, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Animate.exe
    Affected if Adobe Animate is not found on the system, then this CVE does not apply
  2. Identify installed Adobe Animate version
    Right-click Animate.exe, select Properties, then view the Details tab for the Product Version, or use the command: powershell (Get-Item 'C:\Program Files\Adobe\Adobe Animate 2023\Animate.exe').VersionInfo.ProductVersion (adjust path as needed)
    Affected if Version cannot be determined, proceed with other checks
  3. Compare version against affected range for 23.x branch
    Compare the installed version number to the affected range: 23.0.0 through 23.0.14 are vulnerable. Versions 23.0.15 and later are patched
    Affected if Installed version is 23.0.0 through 23.0.14 inclusive (or earlier than 23.0.0 but >= 23.0.0)
  4. Compare version against affected range for 24.x branch
    Compare the installed version number to the affected range: 24.0.0 through 24.0.11 are vulnerable. Versions 24.0.12 and later are patched
    Affected if Installed version is 24.0.0 through 24.0.11 inclusive

If Adobe Animate is installed and the version falls within 23.0.0-23.0.14 or 24.0.0-24.0.11, the environment is affected by this heap-based buffer overflow vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 23.0.15 / 24.0.12 or later
Fixed in 23.0.1524.0.12
Interim mitigation

Update Adobe Animate to the latest patched version once available, and educate users to avoid opening untrusted or unexpected .an and .fla files.

Recommended fix High confidence

Adobe Animate 23.0.15 or 24.0.12

  1. Close Adobe Animate if it is currently running
  2. Navigate to the official Adobe website and download Adobe Animate version 23.0.15 (if currently on version 23.x) or version 24.0.12 (if currently on version 24.x)
  3. Run the downloaded installer and follow the on-screen prompts to complete the update
  4. Restart your computer after the installation completes
  5. Launch Adobe Animate and verify the version by going to Help > About Adobe Animate to confirm the update was successful

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Animate Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61804 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61804 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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