Adobe Photoshop patches multiple code execution flaws
Adobe fixed 13 Photoshop Desktop vulnerabilities that can lead to code execution or crashes via malicious files; no exploitation reported.
Sourceadvisories.ncsc.nl — open the original
What to check
- Applies to
- The 13 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
NCSC-NL published an advisory summarizing Adobe's patches for 13 vulnerabilities in Adobe Photoshop Desktop, including heap-based buffer overflow, out-of-bounds read/write, use-after-free, NULL pointer dereference, divide-by-zero, and uncontrolled recursion issues. These flaws are triggered by processing specially crafted files and require user interaction - an attacker must convince a user to open a malicious file.
Depending on the specific vulnerability, successful exploitation can result in arbitrary code execution in the context of the logged-in user, disclosure of sensitive information through out-of-bounds memory reads, or denial of service through application crashes. CVSS scores range from 5.5 to 7.8, with the higher-severity issues (CVE-2026-113575, CVE-2026-116003, CVE-2026-116480, CVE-2026-117546, CVE-2026-117547) being use-after-free or out-of-bounds write flaws rated 7.8, indicating potential code execution impact.
There is no indication of active exploitation in the wild. Defenders should apply Adobe's released updates for Photoshop Desktop and advise users to exercise caution with files from untrusted sources, given the required user-interaction vector.
Mentioned in this report
Detection guidance
Adobe Photoshop Spawning Shell or Script Interpreter
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Photoshop.exe starting a command shell, script host or LOLBin, which is a plausible post-exploitation sign after a malicious file triggers code execution in Photoshop. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Adobe Photoshop Spawning Shell or Script Interpreter
description: Detects Photoshop.exe spawning command interpreters, script hosts or
common download/execution LOLBins. The advisory describes memory-corruption flaws
in Photoshop triggered by crafted files that can lead to code execution as the user;
this child-process pattern is a generic post-exploitation indicator, not a CVE-specific
signature.
tags:
- attack.execution
- attack.t1203
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: \Photoshop.exe
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \rundll32.exe
- \regsvr32.exe
- \certutil.exe
- \bitsadmin.exe
condition: selection
falsepositives:
- Photoshop scripts or third-party plug-ins that deliberately shell out through cmd.exe
or PowerShell for automation
- Studio pipeline tools that launch helper scripts from Photoshop
level: medium
id: 43542d3c-2966-5a18-8efb-0980d26a5925
status: experimental
author: Vorant
references:
- https://advisories.ncsc.nl/2026/ncsc-2026-0482.html
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://advisories.ncsc.nl/2026/ncsc-2026-0482.html
Free public brief. The detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply) and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs