Skip to content
major vulnerability· requires attention

Unauthenticated remote code execution (CVSS 10.0) in an Adobe enterprise product used to manage customer campaigns; high-impact across organizations hosting ACC.

Applications

CVE-2026-48449

10.0
Critical
EPSS 0.96%Patch availableJul 30, 2026

Unauthenticated RCE in Adobe Campaign Classic allowing arbitrary code execution.

common questions

Is CVE-2026-48449 being exploited?

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

How severe is CVE-2026-48449?

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

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

What does CVE-2026-48449 affect?

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

What should I do about CVE-2026-48449?

Apply vendor patch when available; isolate ACC, restrict access, harden network segmentation 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 (ACC)
impact

Remote attackers can execute arbitrary code as the ACC service user, access/modify campaign data and pivot within networks.

action required

Immediate action required

affected versions
Adobe Adobe Campaign Classic
  • affected<= 7.4.3 build 9397
vendor says fixed in7.4.3 build 9398

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