CVE-2021-28606
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 · uneditedAdobe After Effects version 18.2 (and earlier) is affected by a Stack-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 confidenceAdobe After Effects versions 18.2 and earlier contain a stack-based buffer overflow vulnerability when parsing specially crafted files. An unauthenticated attacker can achieve arbitrary code execution in the context of the current user by tricking a victim into opening a malicious file, requiring user interaction for exploitation.
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<= 18.2CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe After Effects is installedCheck for After Effects installation in typical locations: Windows: C:\Program Files\Adobe\Adobe After Effects [version]\Support Files\, or macOS: /Applications/Adobe After Effects [version]/, or use registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\After Effects in WindowsAffected if After Effects is found on the system
-
Retrieve the installed After Effects version numberWindows: Right-click the After Effects executable (AfterFX.exe) in the installation folder, select Properties, then view the Details tab for Product Version. Alternatively, run: wmic product get name,version | findstr -i "After Effects" or check registry at HKLM\SOFTWARE\Adobe\After Effects\InstalledVersion. macOS: Right-click After Effects.app, Get Info, or run: defaults read /Applications/Adobe\ After\ Effects\* /Contents/Info CFBundleShortVersionStringAffected if Version cannot be determined or shows 18.2 or earlier
-
Compare installed version against affected rangeIf version is retrieved, compare the numeric version to 18.2. Note that version 18.2.1 and later are patched. Versions 18.0, 18.1, 18.2 and earlier are affected.Affected if Installed version is 18.2 or any earlier version (such as 18.0, 18.1, 17.x, etc.)
-
Identify if user interaction risk existsDetermine if the software is used to open project files from external or untrusted sources. This is a file-parsing vulnerability that requires a victim to open a specially crafted malicious file.Affected if Users routinely open .aep or other After Effects project files from unknown or untrusted sources
The environment is affected if Adobe After Effects version 18.2 or earlier is installed and users may open untrusted project files.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe After Effects to version 18.2.1 or later to patch the vulnerability. Avoid opening untrusted or unsolicited After Effects project files from unknown sources.
Adobe After Effects version 18.2.1 or later (or latest available release)
- 1. Open Adobe After Effects on your system
- 2. Navigate to the Help menu and select 'Check for Updates' to see if version 18.2.1 or later is available
- 3. Alternatively, visit the official Adobe website at adobe.com and navigate to the After Effects download page
- 4. Download and install the latest version of Adobe After Effects available
- 5. Verify the installed version by going to Help > About After Effects
- 6. Ensure the installed version is newer than 18.2 (e.g., 18.2.1 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28606 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-28606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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