Adobe patches critical code execution flaws across ColdFusion, AEM, Acrobat
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Multiple Adobe products have critical vulnerabilities allowing arbitrary code execution; no active exploitation reported yet.
Adobe has released security updates addressing multiple vulnerabilities across its product portfolio. The most severe affect ColdFusion, Adobe Experience Manager (AEM), the DNG SDK, Acrobat and Reader, and the Creative Cloud desktop application. ColdFusion vulnerabilities include unsafe file uploads, deserialization flaws, and XXE issues that could lead to arbitrary code execution. AEM contains over 100 stored and DOM-based cross-site scripting vulnerabilities. The DNG SDK has integer overflows and heap buffer overflows. Acrobat and Reader have signature verification and out-of-bounds read issues. Creative Cloud desktop has a temporary file permission vulnerability. Successful exploitation could allow attackers to execute code in the context of the logged-on user, potentially install programs, modify data, or create new accounts depending on user privileges. The advisory notes no current in-the-wild exploitation.
Mentioned in this report
Detection guidance
ColdFusion Server Process Spawning Shell or Script Interpreter
Adobe ColdFusion service process spawning cmd/PowerShell/script hosts or LOLBins, consistent with post-exploitation of file upload, deserialization or XXE flaws. 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: ColdFusion Server Process Spawning Shell or Script Interpreter
description: Detects the Adobe ColdFusion server process (coldfusion.exe / cfusion
runtime) spawning command shells, PowerShell, script hosts or common download LOLBins.
This is typical post-exploitation behaviour after unsafe file upload or deserialization
RCE against ColdFusion. Generalises on the parent/child relation, not on specific
payloads.
tags:
- attack.initial-access
- attack.t1190
- attack.execution
- attack.t1059.001
logsource:
category: process_creation
product: windows
detection:
selection_parent:
- ParentImage|endswith: \coldfusion.exe
- ParentImage|contains: \cfusion\runtime\bin\
selection_child:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \certutil.exe
- \bitsadmin.exe
- \whoami.exe
- \net.exe
- \net1.exe
- \schtasks.exe
condition: selection_parent and selection_child
falsepositives:
- Administrative maintenance scripts or scheduled jobs deliberately invoking cmd.exe
from ColdFusion (cfexecute)
- ColdFusion installer or updater helper scripts run during patching
level: high
id: 55a422fa-b49d-5f39-87ba-d6a229dde626
status: experimental
author: Vorant
references:
- https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-adobe-products-could-allow-for-arbitrary-code-execution_2025-114
Adobe Acrobat or Reader Spawning Shell or Script Interpreter
Acrobat/Reader launching cmd, PowerShell, script hosts or LOLBins, indicating exploitation of a client-side document vulnerability. 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 Acrobat or Reader Spawning Shell or Script Interpreter
description: Detects Adobe Acrobat/Reader processes spawning command shells, PowerShell,
script hosts or common proxy-execution binaries. Reader does not normally launch
these, so the pattern suggests exploitation of a memory-corruption or signature-verification
flaw via a malicious PDF.
tags:
- attack.execution
- attack.t1203
- attack.t1059.001
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith:
- \AcroRd32.exe
- \Acrobat.exe
- \AcroCEF.exe
- \Acrobat Reader DC.exe
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \regsvr32.exe
- \rundll32.exe
- \certutil.exe
- \bitsadmin.exe
- \schtasks.exe
condition: selection
falsepositives:
- PDF workflows or plug-ins that intentionally launch helper scripts, such as some
enterprise document-management integrations
level: high
id: c0f0d010-fc47-5154-a9d7-1001afe1c7b7
status: experimental
author: Vorant
references:
- https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-adobe-products-could-allow-for-arbitrary-code-execution_2025-114
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-114
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 extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 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. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs