Skip to main content
VulnerabilityPublished Updated

CVE-2026-21322: Adobe After Effects · Out-of-bounds Read

Affects Adobe After EffectsSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AdobeAfter EffectsAffected
  • <=25.6
Fixed in–

AI-suggested

  1. Monitor Adobe's official channels for patches and apply updates promptly once available to remediate the vulnerability.
  2. Until patches are released, restrict the opening of After Effects project files from untrusted or unknown sources.
  3. Implement robust endpoint protection solutions with heuristic and behavior-based detection to identify suspicious file parsing or code execution attempts within After Effects.
  4. Employ application whitelisting and sandboxing techniques to limit the execution context and privileges of After Effects processes.
  5. Educate users, especially creative teams, about the risks of opening unsolicited or unexpected project files and encourage verification of file origins.
  6. Use network segmentation to isolate systems running After Effects from critical infrastructure to limit potential lateral movement.
  7. Regularly back up project files and system states to enable recovery in case of compromise.
  8. Consider deploying file integrity monitoring on directories where After Effects files are stored to detect unauthorized changes.
  9. Review and harden user account privileges to minimize the impact of code execution under user context.
  10. Integrate threat intelligence feeds to stay informed about emerging exploits targeting this vulnerability.

Description

After Effects versions 25.6 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

References

Community reviews

Loading reviews…