Arbitrary code execution via out-of-bounds write
Published May 12, 2026 · Updated May 12, 2026
Out-of-bounds write in Adobe Premiere 26.0.2 and Premiere Pro 25.6.4 and earlier allows attackers to execute arbitrary code. Adobe has not disclosed the affected parser, file format, or bounds-checking operation that writes beyond its destination buffer. Exploitation requires a victim to open a malicious file, and successful code runs in the context of the current user.
Summary
What happened
Out-of-bounds write in Adobe Premiere 26.0.2 and Premiere Pro 25.6.4 and earlier allows attackers to execute arbitrary code. Adobe has not disclosed the affected parser, file format, or bounds-checking operation that writes beyond its destination buffer. Exploitation requires a victim to open a malicious file, and successful code runs in the context of the current user.
The record
- CVE
- CVE-2026-34636
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Adobe
- Product
- Premiere
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 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.4
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.
Weakness, pattern, technique
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