Current-user code execution via out-of-bounds write
Published Jul 31, 2026 · Updated Jul 31, 2026
Out-of-bounds write in Adobe Premiere 26.2.2 and earlier and Premiere Pro 25.6.5 and earlier allows attackers to execute code via a malicious file. Adobe identifies the fault only as an out-of-bounds write and has not disclosed the affected parser, file format, or erroneous memory operation. A victim must open the crafted file, after which code runs with the privileges of the current user.
Summary
What happened
Out-of-bounds write in Adobe Premiere 26.2.2 and earlier and Premiere Pro 25.6.5 and earlier allows attackers to execute code via a malicious file. Adobe identifies the fault only as an out-of-bounds write and has not disclosed the affected parser, file format, or erroneous memory operation. A victim must open the crafted file, after which code runs with the privileges of the current user.
The record
- CVE
- CVE-2026-34641
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- Adobe
- Product
- Premiere
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=25.6.5
- Affected versionversion=0 <=26.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo