Code execution via malicious-file out-of-bounds write
Published Sep 8, 2026 · Updated Sep 9, 2026
Out-of-bounds write in Adobe Photoshop 2025 26.11.6 and earlier and Photoshop 2026 27.6 and earlier allows attackers to execute code. Adobe identifies an out-of-bounds memory write but has not disclosed the affected parser, file format, or unchecked operation that writes beyond its destination buffer. Exploitation requires a victim to open a malicious file and runs code in the current user's context, so exposure is limited to that account's privileges.
Summary
What happened
Out-of-bounds write in Adobe Photoshop 2025 26.11.6 and earlier and Photoshop 2026 27.6 and earlier allows attackers to execute code. Adobe identifies an out-of-bounds memory write but has not disclosed the affected parser, file format, or unchecked operation that writes beyond its destination buffer. Exploitation requires a victim to open a malicious file and runs code in the current user's context, so exposure is limited to that account's privileges.
The record
- CVE
- CVE-2026-82005
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Adobe
- Product
- Adobe Photoshop
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 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 <=26.11.6
- Affected versionversion=0 <=27.6
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