After EffectsApplication · Adobe

CVE-2021-28604

HIGH · 7.8 CVSS v3.1 Published 2021-08-24
Fix available
A fix is available. Upgrade to after 18.2 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
Adobe After Effects version 18.2 (and earlier) is affected by a Heap-based Buffer Overflow vulnerability when parsing a specially crafted file. An unauthenticated attacker could leverage this vulnerability to achieve 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 After Effects version 18.2 and earlier contains a heap-based buffer overflow vulnerability when parsing specially crafted files. An attacker can embed malicious data in a file that, when opened by a victim, triggers the overflow and allows arbitrary code execution in the context of the current user.

MitigationUpdate Adobe After Effects to the latest version. Avoid opening files from untrusted or 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
After EffectsApplication
Affected:<= 18.2

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. Locate installed After Effects version
    Open Adobe After Effects and go to Help > About After Effects, or check the application's installation information in your system's program list
    Affected if The displayed version number is 18.2 or lower (for example, 18.2, 18.1, 18.0, 17.x, etc.)
  2. Verify After Effects is present on the system
    Check if Adobe After Effects is installed by looking in the system application list (Windows Settings > Apps, or macOS Applications folder)
    Affected if After Effects version 18.2 or earlier appears in the installed programs list
  3. Confirm the file parsing vulnerability context
    This vulnerability triggers when After Effects opens specially crafted project or media files - no specific system configuration enables this beyond having the application installed
    Affected if After Effects version 18.2 or earlier is present and can be used to open project files

If Adobe After Effects version 18.2 or earlier is installed on the system, the environment is affected by this heap-based buffer overflow vulnerability when parsing untrusted files.

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 a release after 18.2
Interim mitigation

Update Adobe After Effects to the latest version. Avoid opening files from untrusted or unknown sources.

Recommended fix High confidence

After Effects 18.2.1 or later (recommended: latest available version)

  1. 1. Close any running instances of Adobe After Effects
  2. 2. Navigate to the Adobe Creative Cloud desktop application or adobe.com/downloads
  3. 3. Locate Adobe After Effects in your installed applications
  4. 4. Update to the latest available version (version 18.2.1 or later)
  5. 5. Verify the update was successful by checking Help > About After Effects
  6. 6. Ensure all users are warned not to open untrusted or unexpected After Effects project files from unknown sources
Caveat Minor: Some older project files or plugins may require compatibility checking after major version updates; ensure backup of projects before updating

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

Fix this in After Effects Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing0.5 h
  • Review / QA0.5 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-28604 — 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-2021-28604 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