CVE-2026-48367
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 · uneditedAfter Effects is affected by an out-of-bounds write 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 · moderate confidenceAdobe After Effects contains an out-of-bounds write vulnerability that allows arbitrary code execution in the context of the current user. Exploitation requires the victim to open a malicious file, making it a classic file-based memory corruption attack vector.
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<= 25.6.5>= 26.0, <= 26.2.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate After Effects installationOn Windows, check C:\Program Files\Adobe\Adobe After Effects [Version]\Support Files\AfterFX.exe. On macOS, check /Applications/Adobe After Effects [Version]/AfterFX.appAffected if After Effects is installed on the system
-
Determine installed versionOpen After Effects and navigate to Help > About After Effects to display the full version number, or right-click the executable and select Properties > Details to view version informationAffected if version number can be retrieved from the application
-
Compare version against affected rangesCompare your installed version to the vulnerable ranges: versions 25.6.5 and below, or versions 26.0 through 26.2.1Affected if installed version is 25.6.5 or lower, OR between 26.0 and 26.2.1 inclusive
User is affected if Adobe After Effects is installed and the version falls within the vulnerable ranges (25.6.5 and below, or 26.0 through 26.2.1)
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 · scopedApply Adobe security updates for After Effects immediately and educate users to avoid opening files from untrusted sources.
After Effects 25.7+ (for 25.x branch) or 26.3+ (for 26.x branch)
- Check your current After Effects version by opening the application and navigating to Help > About After Effects
- If running version 25.x series (25.6.5 or below), upgrade to version 25.7 or later
- If running version 26.x series (26.0 through 26.2.1), upgrade to version 26.3 or later
- Download the updated version from the official Adobe website at helpx.adobe.com/after-effects
- Restart the application after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48367 — 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-2026-48367 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