Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed ACC endpoint
-
DeliverySubmit crafted code-injection payload
-
ExploitApplication evaluates attacker input
-
ExecutionExecute arbitrary code in user context
-
ImpactPivot across scope-changed boundary
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 | Requires network access to an Adobe Campaign Classic instance that processes attacker-controlled input through a code-evaluation path (CWE-94). Per the vendor vector (AV:N/AC:L/PR:N/UI:N) exploitation needs no user interaction and no authentication against default configurations, and the scope change (S:C) means impact can extend beyond the initially affected component. Limiting factors: the advisory is sparse and names no specific feature, endpoint, or configuration prerequisite, and the description's 'arbitrary code execution in the context of the current user' wording suggests execution may occur within an existing user/session context - verify with Adobe whether an authenticated session is in fact required, which would contradict PR:N. Exposure is further limited to organizations running the affected ACC versions with the vulnerable component reachable. |
| Impact | The vendor CVSS of 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) marks this as maximum-severity: network-reachable, low-complexity, unauthenticated (PR:N), no user interaction, scope-changed, full CIA impact. If those metrics hold, this is a genuine top-priority patch - an unauthenticated remote code-injection (CWE-94) with a scope change into other components. However, several caveats temper the raw score. There is no EPSS score, no CISA KEV listing, and no known public POC, so exploitation status is 'no public exploit identified at time of analysis' - the 10.0 reflects potential impact, not observed activity. The single source is Adobe's own advisory APSB26-142 (the same bulletin that carries sibling CVEs), so the severity is self-reported and not independently corroborated by NVD analysis or third-party research. One internal tension: the description states code executes 'in the context of the current user,' which implies the payload runs with the privileges of an existing/authenticated ACC user session, yet the vector claims PR:N (no privileges) - this pairing should be verified with the vendor, as 'current user' language can indicate a required interactive session rather than purely unauthenticated access. Net: treat as a high-priority patch for exposed ACC instances, but note the 10.0 is a vendor-declared ceiling with no exploitation evidence yet. |
| Exploit ScenarioDerived | An attacker reaches an internet- or intranet-exposed Adobe Campaign Classic instance and submits crafted input that the application interprets as executable code (CWE-94 code injection), triggering arbitrary code execution without any user interaction. Per the CVSS scope change, the injected code can affect resources beyond the initially vulnerable component. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Code injection in Adobe Campaign Classic allows remote attackers to execute arbitrary code in the context of the current user, carrying a maximum-severity CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) with no user interaction required under the vendor vector. The CPE data flags the product with a wildcard version, so the specific affected release range is not enumerated in the supplied intelligence, and Adobe's advisory (APSB26-142) is the only reference. Exploitation status: no public exploit identified at time of analysis; independent analysis cautions that the advisory is sparse and that the description's 'current user' wording may imply an existing session context, so the PR:N unauthenticated rating should be confirmed with Adobe.
RemediationAI
Patch status: patch available per vendor advisory (Adobe APSB26-142), but no exact fixed version is confirmed in the supplied data, so operators must open https://helpx.adobe.com/security/products/campaign/apsb26-142.html and apply the ACC build or hotfix that Adobe lists for their release track. Where an immediate upgrade is not possible, the highest-value compensating control is to restrict network reachability of the Campaign Classic instance so that only trusted administrative networks, VPN segments, or reverse-proxy source ranges can reach it, accepting that this complicates legitimate end-user and API access. Additionally, disable or gate any workflow, scripting, or template-evaluation feature that processes externally supplied content until Adobe clarifies the vulnerable component, and inspect custom JavaScript or JSSP code paths for eval-style constructs fed by user input, trading some campaign automation flexibility for a reduced injection surface. A WAF rule set targeting code-injection payloads in ACC request parameters can absorb opportunistic attempts but has limited value against a low-complexity, scope-changed flaw and may cause false positives on legitimate payloads. Monitor application and web logs for anomalous process spawning, unexpected outbound connections from the ACC host, and unusual workflow executions, since the S:C scope change means post-exploitation activity may appear outside the Campaign Classic process itself.
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'), meaning untrusted input reaches a code-generation or evaluation path rather than a simpler string or command sink. Adobe Campaign Classic is an enterprise marketing-automation platform that ingests campaign definitions, templates, and workflow logic, so any subsystem that compiles or evaluates attacker-influenced content is a plausible injection point; the supplied advisory names no specific endpoint, feature, or configuration prerequisite. The affected asset is identified by the wildcard CPE cpe:2.3:a:adobe:adobe_campaign_classic:*:*:*:*:*:*:*:*, indicating that all tracked versions of the product are treated as vulnerable by the CPE feed rather than a bounded version range. Notably, the vendor vector carries S:C (scope changed), meaning a successful exploit can affect resources beyond the vulnerable component's security authority, which raises the blast radius relative to an unscoped injection flaw and is consistent with code executing under an application identity that can reach downstream systems.
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
Concur with vendor: unauthenticated network code injection (PR:N/AC:L), no UI, scope change per advisory, and RCE yields full C/I/A - though 'current user' context slightly qualifies the PR:N assumption.
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
Adobe Campaign Classic is affected by a maximum-severity code injection vulnerability (CVE-2026-89275, CVSS 10.0) that could allow remote code execution with high confidentiality, integrity, and availability impact. No vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, but the platform's role in campaign operations and customer data makes this a priority risk. Leadership should treat this as requiring urgent containment, vendor confirmation, and patch readiness.
No vendor-released patch identified at time of analysis; interim mitigations include network segmentation and allowlisting for Adobe Campaign Classic, restricting administrative interfaces, enforcing least privilege, deploying WAF/virtual patching for code injection, monitoring for anomalous process creation and outbound traffic, and confirming the PR:N authentication assumption with Adobe.
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 lets any attacker who can reach the server run arbitrary
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
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-84653
GHSA-rv4x-rr36-g73j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB