Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-104347 Overview
CVE-2026-104347 is an out-of-bounds write vulnerability [CWE-787] in Adobe Photoshop Desktop. The flaw allows arbitrary code execution in the context of the current user when a victim opens a malicious file. Adobe disclosed the issue in security bulletin APSB26-158.
Exploitation requires user interaction. An attacker must deliver a crafted file and convince the target to open it in Photoshop. Successful exploitation gives the attacker the same privileges as the logged-in user, enabling malware installation, credential theft, or lateral movement from a workstation.
Critical Impact
Opening a malicious file in Adobe Photoshop Desktop can lead to arbitrary code execution under the current user's privileges.
Affected Products
- Adobe Photoshop Desktop (see Adobe advisory APSB26-158 for affected versions)
- Windows and macOS installations of Photoshop Desktop
- Enterprise and Creative Cloud deployments of Photoshop Desktop
Discovery Timeline
- 2026-10-13 - CVE-2026-104347 published to the National Vulnerability Database (NVD)
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-104347
Vulnerability Analysis
The vulnerability is an out-of-bounds write condition classified under [CWE-787]. Photoshop Desktop writes data past the bounds of an allocated memory buffer while parsing attacker-controlled file content. This memory corruption can overwrite adjacent structures, function pointers, or heap metadata used by the application.
An attacker who controls the overwritten memory can hijack program execution. The result is arbitrary code execution running with the same privileges as the user operating Photoshop. On endpoints where users run with administrative rights, the impact extends to full system compromise.
The attack vector is local and requires user interaction, which aligns with the file-open delivery model. Confidentiality, integrity, and availability are all affected because successful exploitation gives the attacker full control over the Photoshop process.
Root Cause
The root cause is improper validation of input data during parsing of a file format handled by Photoshop. The application does not correctly enforce buffer boundaries before writing data derived from the file, allowing memory outside the intended destination region to be modified. Adobe's advisory APSB26-158 describes the condition and the fixed releases.
Attack Vector
The attack vector is a malicious file crafted to trigger the out-of-bounds write. Typical delivery mechanisms include phishing emails with attached design files, compromised asset libraries, shared project folders, and watering-hole sites distributing booby-trapped documents.
The victim must open the file in Photoshop Desktop. No network listener is involved and no authentication to Photoshop is required. The exploit payload executes in the context of the current user as soon as the file is parsed.
See the Adobe Photoshop Security Update APSB26-158 for vendor-provided technical details.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-104347
Indicators of Compromise
- Unexpected child processes spawned by Photoshop.exe or Adobe Photoshop on macOS, such as command shells, scripting hosts, or rundll32.exe.
- Photoshop process crashes with access violation or heap corruption exceptions shortly after a user opens a file received from an external source.
- Creation of executable files, scheduled tasks, or persistence entries by the Photoshop process.
- Outbound network connections originating directly from the Photoshop process to unfamiliar hosts.
Detection Strategies
- Hunt for process-lineage anomalies where Photoshop is the parent of interpreters (powershell.exe, cmd.exe, wscript.exe, osascript, bash).
- Monitor for memory-corruption telemetry such as application error events, Windows Error Reporting entries, and macOS crash reports tied to Photoshop.
- Correlate file-open events for high-risk extensions (.psd, .psb, .pdf, image formats) with subsequent suspicious process or file-write activity.
Monitoring Recommendations
- Collect endpoint telemetry on process creation, file I/O, and module loads for the Photoshop process on all creative workstations.
- Enable crash and exception logging and forward it to the SIEM for correlation with user-opened files.
- Track Photoshop version inventories to identify endpoints still running unpatched builds.
How to Mitigate CVE-2026-104347
Immediate Actions Required
- Apply the Photoshop Desktop updates listed in Adobe advisory APSB26-158 on all affected endpoints.
- Prioritize patching for users who routinely open files from external parties, clients, or shared storage.
- Instruct users to avoid opening Photoshop files received from untrusted or unverified sources until patching is complete.
Patch Information
Adobe has released fixed versions of Photoshop Desktop. Refer to the Adobe Photoshop Security Update APSB26-158 for the specific fixed version numbers and download instructions. Deploy updates through Creative Cloud Desktop, Adobe Admin Console, or your enterprise software distribution system.
Workarounds
- Run Photoshop under standard user accounts rather than administrative accounts to limit the blast radius of exploitation.
- Block or quarantine Photoshop file formats from untrusted email senders at the mail gateway until patches are deployed.
- Enforce application allowlisting so that processes spawned by Photoshop cannot execute arbitrary binaries or scripts.
# Example: verify installed Photoshop version on Windows
reg query "HKLM\SOFTWARE\Adobe\Photoshop" /s /v Version
# Example: verify installed Photoshop version on macOS
mdls -name kMDItemVersion "/Applications/Adobe Photoshop 2026/Adobe Photoshop 2026.app"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

