Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach internet-facing ACC endpoint
-
DeliverySend crafted code-injection request
-
ExploitImproper code generation evaluates payload
-
ExecutionExecute arbitrary code as current user
-
PersistPivot across changed scope boundary
-
ImpactCompromise host and data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions - remote unauthenticated code execution against default configurations of Adobe Campaign Classic (PR:N, UI:N, AC:L), requiring only network reachability to the ACC server. The description states exploitation does not require user interaction. The primary limiting factor is exposure: risk is greatest for internet-facing or attacker-reachable ACC deployments, whereas instances confined to internal networks behind strong segmentation reduce the practical attack surface. No specific feature toggle, non-default setting, or authentication level is named as a prerequisite in the advisory. |
| Impact | This is a genuine top-priority vulnerability by every structural signal in the input. The vendor CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H yields the maximum 10.0 base score: network attack vector, low complexity, no privileges, no user interaction, scope change, and full high impact to confidentiality, integrity, and availability. As a CWE-94 code-injection reachable pre-authentication, it is the most severe class of flaw and warrants emergency patching for any internet-exposed ACC instance. That said, the exploitation-likelihood signals are ENTIRELY ABSENT, not low: no EPSS score is provided, the CVE is NOT in CISA KEV, no public POC is referenced, and no SSVC decision data (exploitation/automatable/technical-impact) accompanies the record. Exploitation status is therefore 'no public exploit identified at time of analysis' - the 10.0 reflects potential impact and ease of exploitation, not observed activity. This is a single-source, Adobe-self-reported advisory (APSB26-142) with no independent corroboration, so the severity rests wholly on the vendor's own CVSS. No signals conflict; the picture is simply high-impact-but-unproven-in-the-wild. Notably this is the fourth unauthenticated 10.0 CWE-94 code-injection in the same APSB26-142 batch, mirroring CVE-2026-73369, CVE-2026-75699, and CVE-2026-75721 exactly, which reinforces that Adobe found a cluster of pre-auth code-execution defects and treated them uniformly. |
| Exploit ScenarioDerived | An unauthenticated attacker reaches an internet-facing Adobe Campaign Classic server and sends a crafted request that injects attacker-controlled code into a component that improperly generates/evaluates code, achieving arbitrary code execution in the context of the current user with no interaction from any operator. Because scope is changed, the impact can extend beyond the vulnerable component to other resources on the host. No public exploit code is referenced at time of analysis, so exploitation currently requires the attacker to develop their own working payload. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Unauthenticated remote code execution in Adobe Campaign Classic lets any attacker who can reach the server run arbitrary code in the context of the affected process, and the CVSS 3.1 base score is the maximum 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) with scope changed, meaning a successful compromise can cross the component's security boundary and affect resources beyond its intended authority. No user interaction and no authentication prerequisite are required, so the practical exposure is driven almost entirely by whether an ACC instance is reachable from untrusted networks. No public exploit code and no confirmed active exploitation were identified at time of analysis, but the structural severity signals make this a top-priority patch item; Adobe's bulletin APSB26-142 is the authoritative source for fixed builds.
RemediationAI
The primary action is to apply the fix published in Adobe's security bulletin APSB26-142 (https://helpx.adobe.com/security/products/campaign/apsb26-142.html); no specific fixed version number is present in the available input data, so the exact hotfix build must be read directly from that advisory rather than inferred, and patch status should therefore be treated as confirmed-by-vendor-advisory only. Until the update is applied and verified, reduce reachable attack surface: block internet exposure of ACC web/SOAP API endpoints and console ports with upstream firewall or security-group rules and require access through VPN or a zero-trust proxy, accepting the trade-off that remote console users and external integration partners lose direct connectivity and must be re-routed or temporarily suspended. Host-based blocking of outbound traffic from the ACC server process limits post-exploitation staging and payload retrieval but can disrupt legitimate callouts to marketing and analytics integrations, so baseline normal egress first. Generic WAF signatures are of limited value against code-injection flaws where payloads may be syntactically valid application input, so prioritize network isolation over signature filtering. Additionally, enable verbose application and process-level logging on the ACC server and alert on unexpected child-process creation, new scheduled jobs, or anomalous outbound connections; rotate any credentials or API keys stored in or used by the ACC instance on the assumption they may have been exposed, since successful exploitation runs with the privileges of the affected service.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-94, Improper Control of Generation of Code ('Code Injection'), in which attacker-supplied input is incorporated into dynamically generated or evaluated code rather than being constrained to data. Adobe Campaign Classic is a cross-channel marketing automation platform whose runtime exposes web and SOAP APIs and a server-side engine that evaluates expressions, workflow scripts and template logic, so code-generation sinks are architecturally present across the platform; the available advisory data does not identify the specific vulnerable endpoint or evaluation context, and analysts should not assume a particular component. The CVSS vector is notable for the S:C (scope changed) metric, which indicates the vulnerable component does not adequately confine the impact of exploitation, so code executed through this flaw is treated as escaping the originating component's privilege boundary - consistent with the advisory's statement that arbitrary code executes in the context of the current user. With AC:L and PR:N, no non-default configuration or credential is named as a precondition. CPE data (cpe:2.3:a:adobe:adobe_campaign_classic) confirms the affected platform but carries a wildcard version field, meaning exact version cutoffs must be taken from the vendor advisory rather than inferred from the feed.
Know when Adobe Campaign Classic 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
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Unauthenticated remote code injection with no user interaction (AV:N/AC:L/PR:N/UI:N); arbitrary code execution and stated scope change give S:C with full C:H/I:H/A:H.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
Adobe Campaign Classic (ACC) is affected by an Improper Control of Generation of Code ('Code Injection') 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 does not require user interaction. Scope is changed.
Executive ViewAI
A maximum-severity, unauthenticated remote code execution flaw in Adobe Campaign Classic allows anyone who can reach an exposed instance to run arbitrary code with the privileges of the affected process, and its scope-changed rating means a compromise can escape the application boundary and affect adjacent systems and data. Because no authentication or user interaction is required, exposure is determined almost entirely by how many of our Campaign Classic deployments are reachable from untrusted networks - making every internet-facing marketing automation instance a potential enterprise-wide entry point. No vendor patch is available today, so leadership attention should focus on reducing reachability and standing ready to deploy Adobe's fixed builds the moment bulletin APSB26-142 is updated.
No vendor-released patch identified at time of analysis. Interim mitigations: remove or restrict untrusted-network reachability of all Adobe Campaign Classic instances via firewall, load-balancer, VPN, or zero-trust controls; take non-essential externally facing instances offline; deploy web application firewall and network-level filtering; monitor for anomalous process execution, outbound connections, and unexpected administrative changes; rotate service account and integration credentials; and apply vendor fixed builds immediately once published in Adobe bulletin APSB26-142.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Adobe Campaign Classic
View allArbitrary code execution in Adobe Campaign Classic, documented in Adobe security advisory APSB26-142, lets remote attack
Unauthenticated remote code execution in Adobe Campaign Classic (ACC) allows a network-reachable attacker to execute arb
Unauthenticated remote code execution in Adobe Campaign Classic allows an attacker who can reach the application to exec
Remote, unauthenticated attackers can execute arbitrary code in the context of the current application user on systems r
Code injection in Adobe Campaign Classic allows remote attackers to execute arbitrary code in the context of the current
Remote code execution in Adobe Campaign Classic allows an unauthenticated network attacker to invoke functionality that
Arbitrary code execution in Adobe Campaign Classic (ACC) arises from OS command injection (CWE-78), letting an attacker
OS command injection in Adobe Campaign Classic (ACC) allows an attacker to execute arbitrary operating-system commands,
Server-side request forgery in Adobe Campaign Classic (versions up to and including 7.4.4 build 9401) lets remote unauth
Arbitrary code execution in Adobe Campaign Classic allows a low-privileged authenticated attacker to run code in the con
SQL injection in Adobe Campaign Classic (ACC) lets a remote, unauthenticated attacker inject arbitrary SQL commands that
Remote code execution in Adobe Campaign Classic (ACC) arises from server-side template injection (CWE-1336), where impro
EUVD-2026-84666
GHSA-fr85-7pqf-gwjh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB