Adobe patches 100+ flaws across Creative Cloud suite
Adobe released patches for over 100 vulnerabilities across 14 products including Commerce, Photoshop, Illustrator, and InDesign, with the most severe enabling arbitrary code execution.
Sourcecisecurity.org — open the original
What to check
- Applies to
- The 40 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.
Adobe has released security updates addressing more than 100 vulnerabilities across 14 products in its software portfolio. The affected applications span Adobe Commerce/Magento, Creative Cloud tools (Photoshop, Illustrator, InDesign, InCopy, Animate), and the Substance 3D suite (Viewer, Modeler, Painter, Sampler, Stager), as well as FrameMaker and Dimension. The most severe vulnerabilities could allow attackers to achieve arbitrary code execution in the context of the logged-on user.
The vulnerability types include out-of-bounds write and read conditions, use-after-free flaws, heap-based and stack-based buffer overflows, NULL pointer dereferences, and privilege escalation issues. Adobe Commerce is affected by application denial-of-service, privilege escalation, arbitrary file system read, and security feature bypass vulnerabilities. The MS-ISAC has classified these as requiring immediate patching but notes there are currently no reports of active exploitation in the wild.
Organizations should prioritize patching based on which Adobe products are deployed in their environments. The vulnerabilities require user interaction to exploit, typically through opening malicious files in the affected applications. Successful exploitation depends on the privileges of the logged-on user, with administrative accounts presenting higher risk than restricted user accounts.
Mentioned in this report
Detection guidance
Suspicious Child Process Spawned from Adobe Creative Cloud/Reader Applications
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects command/script interpreters or LOLBins spawned as children of Adobe Creative Cloud, Substance 3D, or Acrobat processes, consistent with exploitation of a client-side vulnerability after opening a malicious file. 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: Suspicious Child Process Spawned from Adobe Creative Cloud/Reader Applications
id: e8d771d8-804e-5f77-bbb7-44b51ba0aaef
status: experimental
description: Detects command/script interpreters or LOLBins spawned as children of
Adobe Creative Cloud, Substance 3D, or Acrobat processes, consistent with exploitation
of a client-side vulnerability after opening a malicious file.
references:
- https://helpx.adobe.com/security.html
author: Vorant
tags:
- attack.t1203
- attack.execution
logsource:
category: process_creation
product: windows
detection:
parent_selection:
ParentImage|endswith:
- \Photoshop.exe
- \Illustrator.exe
- \InDesign.exe
- \InCopy.exe
- \Animate.exe
- \FrameMaker.exe
- \Dimension.exe
- \Acrobat.exe
- \AcroRd32.exe
- \Substance3DPainter.exe
- \Substance3DSampler.exe
- \Substance3DStager.exe
- \Substance3DViewer.exe
- \Substance3DModeler.exe
child_selection:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \rundll32.exe
- \regsvr32.exe
- \certutil.exe
- \bitsadmin.exe
filter_updater:
CommandLine|contains:
- AdobeARM
- AdobeUpdater
- CCXProcess
- \Adobe\OOBE\
condition: parent_selection and child_selection and not filter_updater
falsepositives:
- Adobe auto-update helper processes launching legitimate update scripts
- Enterprise software deployment tools invoking scripting engines from Adobe install
directories
level: high
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-adobe-products-could-allow-for-arbitrary-code-execution_2025-071
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,433 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