Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-89275 – Unauthenticated RCE via Code Injection – Adobe Campaign Classic ≤ 7.4.4 build 9401

Be the first to know when new zero-days emerge:

Summary

CVE-2026-89275 is a critical code injection vulnerability (CWE-94, Improper Control of Generation of Code) in Adobe Campaign Classic (ACC). The flaw allows an unauthenticated, remote attacker to achieve arbitrary code execution in the context of the current user, with no user interaction required. Adobe rates this issue as Critical with the maximum CVSS v3.1 base score of 10.0 and has released a Priority 1 fix under security bulletin APSB26-142.

Technical details

  • Root cause: Adobe Campaign Classic fails to properly control the generation of code from attacker-supplied input, allowing injected code to be executed by the application (CWE-94).
  • Trigger conditions: No authentication and no user interaction are required to exploit the flaw, and the attack complexity is low.
  • Attack vector: Network — the vulnerability is remotely exploitable over the network against exposed Campaign Classic instances.
  • Impact: Successful exploitation results in arbitrary code execution in the context of the current user, with high impact to confidentiality, integrity, and availability, and a changed scope (the attacker can affect resources beyond the vulnerable component).
  • Deployment scope: The issue affects fully on-premise deployments of Adobe Campaign Classic and the on-premise components of hybrid deployments. Adobe-hosted (cloud) instances were already remediated by Adobe and require no customer action.

Affected software

  • Adobe Campaign Classic (ACC) — all versions from 0 through 7.4.4 build 9401, on both Windows and Linux.

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade on-premise Adobe Campaign Classic deployments to version 7.4.4 build 9402 or later, as provided in Adobe Security Bulletin APSB26-142.
  • If immediate patching is not possible: Restrict network exposure of Campaign Classic management and application interfaces to trusted networks only (e.g., VPN or allow-listed IP ranges), and closely monitor Campaign Classic servers for anomalous process execution or unexpected outbound connections until the patch can be applied. Cloud/Adobe-hosted instances do not require action, as Adobe has already remediated them.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge