ADOBE PREMIERE · CVE-2026-82012 · Package
FIX → 26.5.3 · 27.0 ✓ verified
Adobe Premiere Pro has an out-of-bounds write flaw that lets a crafted file corrupt memory. An attacker who gets a victim to open that file can run code as the current user.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running Adobe Premiere on Windows or macOS at 26.5.2 or earlier, or 25.6.6 or earlier. Exploitation needs the user to open a malicious project or media file, so editors who receive files from outside are the main concern. Teams that do not use Premiere can skip it.
Not affected if no-untrusted-files, premiere-26.5.3-or-later, premiere-27.0-or-later
Who cares adobe, desktop, macos, premiere-pro, user-interaction, video-editing, windows
26.5.2 or earlier, or 25.6.6 or earlier (Windows and macOS); fixed in 26.5.3 and 27.0Premiere Pro 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.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 26.5.3 · 27.0
Update Adobe Premiere to 26.5.3 (26.x line) or 27.0 via Creative Cloud / Download Center