After EffectsApplication · Adobe

CVE-2025-27204

MEDIUM · 5.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 24.6.5 / 25.2 or later.
See remediation →
58/100
Remediation priority · Elevated
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 versions 25.1, 24.6.4 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 · moderate confidence

Adobe After Effects contains an out-of-bounds read vulnerability that allows reading memory beyond allocated buffers. This can expose sensitive memory contents including addresses that help attackers bypass ASLR. Exploitation requires a victim to open a specially crafted malicious file.

MitigationUsers should avoid opening files from untrusted sources and update to the latest version of After Effects once Adobe releases a patch for this vulnerability.

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:< 24.6.5>= 25.0, < 25.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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 on Windows
    Open Adobe Creative Cloud desktop app, go to the 'Apps' tab, find After Effects in the installed apps list and note the version number displayed
    Affected if The displayed version is lower than 24.6.5, or is between 25.0 and 25.1.x inclusive
  2. Locate installed After Effects version on macOS
    Open Adobe Creative Cloud desktop app, go to the 'Apps' tab, find After Effects in the installed apps list and note the version number displayed
    Affected if The displayed version is lower than 24.6.5, or is between 25.0 and 25.1.x inclusive
  3. Check version from Within After Effects
    Launch After Effects, go to Help > About After Effects. The version number appears in the dialog that opens
    Affected if The version shown is less than 24.6.5, or is 25.0, 25.1, or 25.1.x
  4. Check Windows Registry for version
    Open Registry Editor and navigate to HKLM\SOFTWARE\Adobe\After Effects\InstallPath\, or look in HKLM\SOFTWARE\WOW6432Node\Adobe\After Effects\InstallPath\ for the version key
    Affected if The Version value found is less than 24.6.5, or falls between 25.0 and 25.2 (exclusive)
  5. Verify macOS Application bundle version
    In Finder, navigate to /Applications/Adobe After Effects, right-click the app, select Show Package Contents, open Info.plist and look for CFBundleShortVersionString
    Affected if The CFBundleShortVersionString value is below 24.6.5, or is 25.0, 25.1, or 25.1.x

Your environment is affected if the installed Adobe After Effects version is either below 24.6.5 or falls within the 25.0 to 25.1.x range.

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 24.6.5 / 25.2 or later
Fixed in 24.6.525.2
Interim mitigation

Users should avoid opening files from untrusted sources and update to the latest version of After Effects once Adobe releases a patch for this vulnerability.

Recommended fix High confidence

24.6.5 or 25.2

  1. Upgrade Adobe After Effects to version 24.6.5 or later for the 24.x release line
  2. Upgrade Adobe After Effects to version 25.2 or later for the 25.x release line
  3. Verify the installed version by opening After Effects and checking the About dialog

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

Fix this in After Effects Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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