Skip to main content

Adobe Photoshop EUVDEUVD-2026-100690

| CVE-2026-95635 HIGH
Double Free (CWE-415)
2026-10-13 psirt@adobe.com GHSA-8p6g-q386-cv37
7.8
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver crafted malicious file to victim
  2. Delivery
    Victim opens file in Photoshop
  3. Exploit
    Trigger double free during parsing
  4. Execution
    Corrupt heap for code execution
  5. Impact
    Run arbitrary code as current user

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Double free prevention
Exploitation Conditions

Exploitation requires the victim to open an attacker-supplied malicious file in Photoshop Desktop (UI:R) - there is no remote or unauthenticated network trigger. The affected configurations are Photoshop Desktop versions ≤27.10 and ≤26.11.7 per the EUVD record; default installations are vulnerable with no special feature or non-default setting called out in the advisory. Key limiting factors: the attack vector is local (AV:L), so the attacker must get the crafted file onto the victim's system and the victim must actively open it in Photoshop; code runs only at the current user's privilege level (S:U, no privilege escalation), so impact is bounded by that user's rights rather than granting system-level control.

Impact

This is a credible but not emergency-level priority. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8 HIGH) describes a local, low-complexity flaw that needs no attacker privileges but DOES require user interaction - the victim must open a malicious file. That UI:R plus AV:L combination is the decisive risk-limiter: this is not a wormable, remotely-triggerable network bug but a classic file-format/memory-corruption issue that depends on social engineering to deliver the crafted file. On exploitation signals, the picture is reassuring but incomplete: no EPSS score was provided in the input, there is no CISA KEV listing, and no public POC is referenced, so exploitation status is 'no public exploit identified at time of analysis.' SSVC-style reading: exploitation=none observed, automatable=no (requires per-victim user interaction), technical impact=total (C:H/I:H/A:H, code execution as the current user). The signals are internally consistent - a high CVSS driven by impact severity rather than by ease/breadth of exploitation. Double Free (CWE-415) bugs are realistically weaponizable into code execution by skilled actors, so the HIGH rating is justified, but absent KEV/POC/EPSS data this should be patched on a normal prioritized cycle rather than treated as an active-exploitation fire drill.

Exploit ScenarioDerived

An attacker crafts a malicious Photoshop-parseable file (e.g. a booby-trapped image/document) and delivers it via email, a shared drive, or a download, luring the victim into opening it in Photoshop Desktop. Parsing triggers the double free in CWE-415, which an attacker grooms into memory corruption and arbitrary code execution running with the privileges of the current user. No public exploit code is identified at time of analysis, so working exploitation would require the attacker to develop the primitive themselves.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Opening a maliciously crafted file in Adobe Photoshop Desktop (27.10 and earlier, and 26.11.7 and earlier) can trigger a double-free memory-corruption condition that results in arbitrary code execution in the context of the current user. The flaw carries a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), reflecting that the attacker cannot reach the target over the network and must rely on the victim opening the file, and that code executes only with the privileges of the logged-on user rather than escalating to system level; adversary value is therefore tied to social-engineering delivery of a weaponised document, and there is no public exploit identified at time of analysis. The independent assessment rates this as a credible but not emergency-level priority, consistent with the local attack vector and user-interaction requirement; no CISA KEV listing or public proof-of-concept was supplied in the source data.

RemediationAI

The provided data does not state an exact fixed version, so patch status is best described as not confirmed from the available intelligence: consult Adobe's advisory APSB26-158 (https://www.adobe.com/trust/security/products/photoshop/apsb26-158.html) and the Creative Cloud updater for the vendor-released patched build covering the 27.x and 26.x tracks; because the EUVD record lists the affected ranges as 27.10-and-earlier and 26.11.7-and-earlier, remediation is expected in a later release than those numbers, but no fix version should be assumed until confirmed by Adobe. Until the update is applied, the most effective compensating control is to prevent crafted files from ever reaching the parser: block or strip PSD/PSB and other Photoshop-associated attachment types (and archive files containing them) at the mail gateway and web download proxy, and restrict write access to shared folders that feed production workstations - the trade-off is that legitimate design-file workflows relying on email or shared drives will break and need an approved transfer channel. Run Photoshop under a standard, non-administrative user account so the S:U scope keeps code execution bounded to that user's rights, and isolate the application with OS-level sandboxing, AppContainer/low-integrity enforcement or an EDR exploit-protection policy that covers Photoshop.exe; these measures reduce blast radius but can cause plug-in and scratch-disk compatibility problems. For high-risk teams, process untrusted or externally sourced image files on a dedicated, network-isolated machine before opening them on production systems, and disable automatic opening/preview of files from untrusted sources in the OS and in Photoshop; none of these workarounds removes the underlying memory-corruption bug, so they should be treated as temporary mitigations until the vendor patch is confirmed and deployed.

Affected VersionsENISA

Photoshop 0 ≤27.10
Photoshop 0 ≤26.11.7

Affected Packages

euvd photoshop no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-415, Double Free, in Adobe Photoshop's file-parsing code path - the same heap allocation is released twice, and the second release operates on memory that may already have been reallocated by another object, giving an attacker a controllable write primitive that can be shaped into arbitrary code execution. Photoshop consumes a large number of complex binary formats (PSD/PSB, TIFF, RAW and camera-specific formats, plus third-party plug-ins), and this class of bug typically lives in a parser that manages chunked or nested memory structures where error-handling paths free a buffer and then free it again on cleanup. The supplied CVSS vector confirms attacker prerequisites precisely: AV:L means the crafted file must be delivered to and opened on the victim's machine (email attachment, download, shared drive, removable media), PR:N means no prior credentials or privileges on the target are needed, and UI:R means the victim must actively open the file in Photoshop - there is no unauthenticated remote trigger. ACL:L indicates no special preconditions beyond that, and S:U with C:H/I:H/A:H means full compromise of confidentiality, integrity and availability within the user's own security context only. The EUVD record (EUVD-2026-100690) identifies the affected builds as Photoshop 0 ≤ 27.10 and 0 ≤ 26.11.7; no CPE strings were included in the provided intelligence, so platform-level matching should be taken from Adobe advisory APSB26-158, which covers the Photoshop Desktop tracks for both current and prior major versions. The vulnerability was reported through Adobe's PSIRT (psirt@adobe.com) and is tagged RCE.

Know when Adobe gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (adobe) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

File must be opened locally by the user so AV:L and UI:R; no attacker privileges needed (PR:N); double free yields code execution as current user giving full C/I/A impact with no scope change.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Photoshop Desktop is affected by a Double Free vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Executive ViewAI

Why It Matters

Adobe Photoshop Desktop users across the organization are exposed to a high-severity memory-corruption flaw that could allow an attacker to execute code as the logged-in user if a malicious file is opened. Exploitation requires user interaction and no public exploit identified at time of analysis, so the immediate risk is targeted social engineering rather than broad, automated compromise. Leadership should care because this widely deployed creative tool could be used as an entry point for user-level data theft or further lateral movement, and no vendor-released patch identified at time of analysis.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include avoiding untrusted files, running Photoshop with least privilege, disabling preview handlers for PSD/PSB files, filtering email/web attachments, and applying application control or sandboxing.

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
High
Adobe Photoshop is a very widely deployed desktop creative application
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in Adobe

View all
CVE-2015-5119 CRITICAL POC
9.8 Jul 08

Remote code execution in Adobe Flash Player 11.x through 18.x allows unauthenticated network attackers to execute arbitr

CVE-2016-4117 CRITICAL POC
9.8 May 11

Remote code execution in Adobe Flash Player 21.0.0.226 and earlier allows unauthenticated network attackers to execute a

CVE-2015-3113 CRITICAL POC
9.8 Jun 23

Adobe Flash Player contains a heap-based buffer overflow that allows remote code execution, exploited as a zero-day in J

CVE-2011-2462 CRITICAL POC
9.8 Dec 07

Adobe Reader and Acrobat contain an unspecified U3D component vulnerability causing memory corruption that allows remote

CVE-2011-0611 HIGH POC
8.8 Apr 13

Adobe Flash Player contains a type confusion vulnerability in object handling that allows remote attackers to execute ar

CVE-2009-0927 HIGH POC
8.8 Mar 19

Adobe Reader and Acrobat 9.x, 8.x, and 7.x contain a stack-based buffer overflow in the getIcon method of the Collab obj

CVE-2014-0497 CRITICAL POC
9.8 Feb 05

Integer underflow in Adobe Flash Player before 11.7.700.261 and 11.8.x through 12.0.x before 12.0.0.44 on Windows and Ma

CVE-2009-4324 HIGH POC
7.8 Dec 15

Adobe Reader and Acrobat contain a use-after-free vulnerability in the Doc.media.newPlayer JavaScript method that was ac

CVE-2015-0313 CRITICAL POC
9.8 Feb 02

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.269 and 14.x through 16.x before 16.0.0.305 on Windows

CVE-2015-5122 CRITICAL POC
9.8 Jul 14

Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player

CVE-2015-0311 CRITICAL POC
9.8 Jan 23

Unspecified vulnerability in Adobe Flash Player through 13.0.0.262 and 14.x, 15.x, and 16.x through 16.0.0.287 on Window

CVE-2013-0632 CRITICAL POC
9.8 Jan 17

administrator.cfc in Adobe ColdFusion 9.0, 9.0.1, 9.0.2, and 10 allows remote attackers to bypass authentication and pos

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy