ADOBE PREMIERE · CVE-2026-110086 · Other
FIX → 27.0 · 26.5.3 ✓ verified
Adobe Premiere Pro has an out-of-bounds write flaw that lets an attacker run code with the privileges of the logged-in user. Exploitation requires a victim to open a malicious file.
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 (Windows or macOS) at 26.5.2 or earlier, or 25.6.6 or earlier, who opens a crafted project or media file. Code runs with the logged-in user's rights (local attack vector, user must open the file). Teams that do not use Premiere, or only open files from trusted sources, can skip it.
Not affected if files-from-trusted-sources-only, no-premiere-pro-installed
Who cares adobe, creative-workstations, macos, premiere-pro, windows
26.5.2 and earlier, or 25.6.6 and earlier26.5.3 or 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 27.0 · 26.5.3
26.5.3 if you stay on the 26.x line, via Creative Cloud or the Download Center (Adobe APSB26-101)25.6.6, and the bulletin gives no fixed 25.x version, so move to 26.5.3 or 27.0