Skip to content
major vulnerability· requires attention

10.0 RCE in widely deployed Adobe enterprise product (Campaign Classic); unauthenticated/no-interaction code execution can lead to org-wide compromise.

Applications

CVE-2026-89275

10.0
Critical
EPSS 1%Patch availableSep 23, 2026

Critical RCE in Adobe Campaign Classic allowing remote arbitrary code execution.

common questions

Is CVE-2026-89275 being exploited?

Not confirmed. CVE-2026-89275 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.

How severe is CVE-2026-89275?

CVE-2026-89275 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-89275?

Yes. A fix has been recorded for CVE-2026-89275. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-89275 affect?

CVE-2026-89275 affects Adobe Campaign Classic. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-89275?

Apply Adobe's patch immediately; restrict access to Campaign servers and monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Adobe Campaign Classic
impact

Remote arbitrary code execution in application context without user interaction; attackers can run code, pivot, and exfiltrate data or achieve full system compromise.

action required

Immediate action required

affected versions
Adobe Adobe Campaign Classic
  • affected<= 7.4.4 build 9401
vendor says fixed in7.4.4 build 9402

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free