Severity by source
AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
File must be opened locally so AV:L/UI:R; 'conditions beyond attacker control' justify AC:H; no auth needed (PR:N); code execution escapes the app boundary (S:C) with full C/I/A impact.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
Lifecycle Timeline
2DescriptionCVE.org
Animate is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the current user. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue requires user interaction in that a victim must open a malicious file. Scope is changed.
AnalysisAI
Arbitrary code execution in Adobe Animate 2023 and 2024 arises from an Incorrect Authorization flaw (CWE-863) that lets a maliciously crafted file run code in the context of the current user. Exploitation requires the victim to open the attacker-supplied file and depends on conditions beyond the attacker's control, and there is no public exploit identified at time of analysis. Adobe self-reported the issue and published fixes in advisory APSB26-83.
Technical ContextAI
Adobe Animate is a desktop authoring application for interactive animation, HTML5/Canvas content, and legacy Flash-format (FLA/XFL) assets. The CPE data pins the affected software to cpe:2.3:a:adobe:adobe_animate_2023 and cpe:2.3:a:adobe:adobe_animate_2024, i.e. the 2023 and 2024 release lines. The root cause is CWE-863 (Incorrect Authorization): the application makes a flawed authorization decision when handling a crafted project/media file, permitting an operation that should be denied. Because the CVSS marks Scope as Changed (S:C), the code execution escapes the vulnerable component's authorization boundary and impacts resources managed by another security authority (the underlying user session/OS), which is why the impact is full code execution as the current user rather than a contained fault.
RemediationAI
Update Adobe Animate 2023 and 2024 to the fixed builds released by Adobe; consult advisory APSB26-83 (https://helpx.adobe.com/security/products/animate/apsb26-83.html) for the exact patched version numbers, as they are not specified in the available data (Patch available per vendor advisory). Because the attack requires a victim to open a malicious file, the most effective compensating control until patching is to avoid opening Animate project or media files (FLA/XFL and imported assets) from untrusted or unverified sources, and to restrict such files at the email/download gateway; the trade-off is workflow friction for teams that legitimately exchange Animate assets. Running Animate under a least-privileged user account limits the blast radius of code execution but does not prevent the exploit. Apply the update on the normal Adobe patch cycle given the local vector and required user interaction.
More in Adobe Animate 2023
View allArbitrary code execution in Adobe Animate 2023 and 2024 stems from a path traversal weakness triggered when a victim ope
Arbitrary code execution in Adobe Animate 2023 and 2024 allows an attacker to run commands in the context of the current
Arbitrary code execution in Adobe Animate 2023 and 2024 stems from an incorrect authorization (CWE-863) weakness that le
Arbitrary code execution in Adobe Animate 2023 and 2024 arises from an untrusted search path (CWE-426) flaw that lets a
Arbitrary code execution in Adobe Animate 2023 and 2024 allows an attacker to run OS commands in the context of the curr
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-44437
GHSA-g3c2-8rh7-fvm4