CVE-2026-21351: Adobe After Effects · Use After Free
Affects Adobe After EffectsSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AdobeAfter Effects | Affected
| Fixed in– |
AI-suggested
Until an official patch is released by Adobe, organizations should implement the following mitigations: 1) Educate users to avoid opening After Effects files from untrusted or unknown sources. 2) Employ application whitelisting and restrict execution of unauthorized files. 3) Use endpoint detection and response (EDR) tools to monitor for suspicious behavior related to After Effects processes. 4) Implement network segmentation to limit the impact of a compromised system. 5) Regularly back up critical project files and data to enable recovery in case of compromise. 6) Consider running After Effects in a sandboxed or isolated environment to contain potential exploitation. 7) Monitor Adobe’s security advisories closely and apply patches immediately upon release. 8) Limit user privileges where possible to reduce the impact of code execution under user context.
Description
After Effects versions 25.6 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.