CVE-2026-76193: Adobe Campaign Classic (ACC) Server-Side Request Forgery (SSRF) vulnerability
CVE-2026-76193 affects Adobe Campaign Classic (ACC). The reported consequence is code execution, meaning successful exploitation could make the affected application or process run attacker-controlled code.
What happened
CVE-2026-76193: Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in arbitrary code execution in the co. A security weakness in Adobe Campaign Classic (ACC) is being tracked as CVE-2026-76193. CVE-2026-76193 affects Adobe Campaign Classic (ACC).
CVE-2026-76193 currently carries a CRITICAL 10 severity signal in the retained vulnerability data. The reported consequence is code execution, meaning successful exploitation could make the affected application or process run attacker-controlled code. An attacker could exploit this vulnerability to execute arbitrary code.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
An attacker could exploit this vulnerability to execute arbitrary code.
Exploitation of this issue does not require user interaction.
CVE-2026-76193 currently carries a CRITICAL 10 severity signal in the retained vulnerability data.
Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) 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.
A security weakness in Adobe Campaign Classic (ACC) is being tracked as CVE-2026-76193. The reported consequence is code execution, meaning successful exploitation could make the affected application or process run attacker-controlled code. The description places that code execution in the context of the current user, so the practical impact depends partly on what that user account can access. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. The issue currently carries a CRITICAL 10 severity signal in the available reporting.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
Adobe Campaign Classic (ACC) is present and the vulnerable function or code path is reachable in normal application use.
attacker-controlled input or the relevant workflow reaches the the reported vulnerability condition described in the advisory.
the the reported vulnerability condition is triggered inside Adobe Campaign Classic (ACC), creating the security boundary failure described by the advisory.
successful exploitation can result in attacker-controlled code execution in the affected application or process.
the reported impact is tied to the current user context, so the attacker's effective access depends on that user's permissions.
Why this matters to you
CVE-2026-76193 matters because the practical risk is not the score alone — it is whether Adobe Campaign Classic (ACC) exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is CRITICAL 10. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of Adobe Campaign Classic (ACC).
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for Adobe Campaign Classic (ACC).
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.