ADOBE PREMIERE · CVE-2026-110085 · Other
FIX → 27.0 · 26.5.3 ✓ verified
Adobe Premiere Pro has an out-of-bounds write flaw that lets a crafted file write past a memory buffer. An attacker who gets a victim to open that file can run code with the victim's user rights.
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 on the older line) who opens a crafted project or media file. Exploitation needs the user to open a malicious file; Adobe is not aware of exploitation in the wild. Teams that never open files from outside sources are at lower risk.
Not affected if no-untrusted-files
Who cares adobe, macos, premiere, premiere-pro, user-interaction, windows
26.5.2 and earlier, or 25.6.6 and earlier (Windows and macOS)26.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
Update Adobe Premiere to 27.0 or 26.5.3 (Creative Cloud app or Download Center).