Skip to content
major vulnerability· requires attention

Authz bypass leading to unauthenticated/no-interaction RCE in Adobe Campaign Classic — enterprise marketing platform with broad usage and high-impact potential.

Applications

CVE-2026-75728

9.1
Critical
EPSS 1%Patch availableSep 23, 2026

Authorization bypass in Adobe Campaign Classic enabling arbitrary code execution without user interaction.

common questions

Is CVE-2026-75728 being exploited?

Not confirmed. CVE-2026-75728 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.0% probability of exploitation in the next 30 days.

How severe is CVE-2026-75728?

CVE-2026-75728 is rated Critical with a CVSS score of 9.1. 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-75728?

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

What does CVE-2026-75728 affect?

CVE-2026-75728 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-75728?

Install Adobe APSB26-142 update immediately; isolate affected hosts and audit 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

Authorization bypass allows remote arbitrary code execution as the affected service user; attacker can run commands, deploy malware, exfiltrate data, and pivot.

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