dbcve.org
After EffectsApplication · Adobe

CVE-2026-34690

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 25.6.5 / 26.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
After Effects is affected by a Stack-based Buffer Overflow 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.

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

After Effects contains a stack-based buffer overflow vulnerability that can be triggered when parsing a specially crafted malicious file. Successful exploitation allows an attacker to execute arbitrary code in the context of the current user, requiring the victim to open the malicious file as the sole user interaction needed.

MitigationUsers should avoid opening After Effects project files from untrusted sources and apply available vendor patches promptly. Organizations should implement file type restrictions and user awareness training regarding the risks of opening unsolicited attachments.

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:< 25.6.5>= 26.0, < 26.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. Check if After Effects is installed
    Look for Adobe After Effects in the system. On Windows, check Program Files/Adobe or use the Add/Remove Programs list. On macOS, check /Applications for Adobe After Effects.
    Affected if After Effects is present on the system
  2. Find the installed version number
    Open After Effects and go to Help > About After Effects, or check the application properties in the system installer/registry.
    Affected if Unable to determine the version number
  3. Compare version against affected ranges
    The affected versions are: anything less than 25.6.5, OR version 26.0 through any version less than 26.2. Compare your installed version to these ranges.
    Affected if Installed version falls below 25.6.5 OR is 26.0 to below 26.2
  4. Confirm the vulnerability trigger condition
    The vulnerability is triggered when After Effects parses specially crafted malicious files. The flaw exists in the file parsing functionality regardless of configuration.
    Affected if After Effects can open and parse project files (this is the default behavior)

If Adobe After Effects is installed and the version is either below 25.6.5 or between 26.0 and 26.2 (exclusive), the environment is affected by this CVE.

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 25.6.5 / 26.2 or later
Fixed in 25.6.526.2
Interim mitigation

Users should avoid opening After Effects project files from untrusted sources and apply available vendor patches promptly. Organizations should implement file type restrictions and user awareness training regarding the risks of opening unsolicited attachments.

Recommended fix High confidence

25.6.5 or 26.2 (first fixed release depends on your current major version line)

  1. Close After Effects completely before installing any updates
  2. Back up your current projects and settings as a precaution
  3. Open Adobe Creative Cloud desktop app or visit the official Adobe downloads page
  4. Navigate to After Effects and check for available updates
  5. Install version 25.6.5 (if currently on versions before 25.6.5) OR version 26.2 (if currently on versions 26.0 or 26.1)
  6. After installation, launch After Effects and verify the installed version in the About menu
Caveat Standard update - minor interface or feature changes possible but no known breaking project incompatibilities

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

Fix this in After Effects Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34690 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2026-34690 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