dbcve.org
AnimateApplication · Adobe

CVE-2025-27200

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 23.0.11 / 24.0.8 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 24.0.7, 23.0.10 and earlier are affected by a Use After Free 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 · high confidence

Adobe Animate versions 24.0.7, 23.0.10 and earlier contain a Use After Free vulnerability that allows arbitrary code execution in the context of the current user when a victim opens a specially crafted malicious file.

MitigationUpdate Adobe Animate to the latest patched version. Until patched, warn users to avoid opening untrusted .SWF, .FLV, or Animate project files from unknown sources.

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.11>= 24.0.0, < 24.0.8

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. Check installed Adobe Animate version on Windows
    Open Windows Registry Editor and navigate to HKLM\SOFTWARE\Adobe\Adobe Animate\24.0 (or 23.0), or use command: reg query 'HKLM\SOFTWARE\Adobe\Adobe Animate' /v Version
    Affected if The reported version falls within 23.0.0-23.0.10 or 24.0.0-24.0.7 (the version string is less than 23.0.11 or 24.0.8)
  2. Check installed Adobe Animate version via application menu
    Launch Adobe Animate, then go to Help > About Adobe Animate to view the exact version number displayed in the dialog
    Affected if The displayed version is 23.0.10 or earlier, or 24.0.7 or earlier
  3. Check file type associations for vulnerable formats
    In Windows, open Default Apps > Choose default apps by file type, and verify if .SWF, .FLV, or .FLA files are associated with Adobe Animate; alternatively, check HKCR\.swf\OpenWithProgids in Registry
    Affected if Adobe Animate is set as the default handler for .SWF, .FLV, or Animate project files and the version is in the affected range
  4. Check for recent file opening activity
    Review recent documents or temp folders for .SWF, .FLV, or .FLA files that may have been opened; on Windows, check the JumpList or Recent folder at %APPDATA%\Adobe\Adobe Animate\en\Recent Files
    Affected if The user has recently opened .SWF, .FLV, or Animate project files from untrusted or unknown sources while running a vulnerable version

A user is affected if Adobe Animate version is 23.0.0-23.0.10 or 24.0.0-24.0.7 AND the application is used to open .SWF, .FLV, or Animate project files, particularly from untrusted sources.

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.11 / 24.0.8 or later
Fixed in 23.0.1124.0.8
Interim mitigation

Update Adobe Animate to the latest patched version. Until patched, warn users to avoid opening untrusted .SWF, .FLV, or Animate project files from unknown sources.

Recommended fix High confidence

Adobe Animate 23.0.11 or 24.0.8

  1. Close any running instances of Adobe Animate
  2. Back up current projects as a precaution
  3. Download Adobe Animate version 23.0.11 (for 23.x users) or version 24.0.8 (for 24.x users) from the official Adobe website or through the Creative Cloud desktop application
  4. Install the updated version following the on-screen prompts
  5. Restart your computer after installation completes
  6. Verify the installed version by opening Animate and checking Help > About Adobe Animate
Caveat Security patch update; review Adobe release notes for any minor feature changes

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

Fix this in Animate Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-27200 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