← console
voxell vciy

CVE-2026-76193: Adobe Campaign Classic (ACC) | Server-Side Request Forgery (SSRF) (CWE-918)

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to ACC v7: 7.4.4 build 9401 or later CVE record
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

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.

weakness
CWE-918 Server-Side Request Forgery (SSRF) (CWE-918)
affected
Adobe Campaign Classic
published ranges
adobe campaign <= 7.3.2; adobe campaign 7.4.1-9383; adobe campaign 7.4.2-9390; adobe campaign 7.4.2-9391; and 6 more on the CVE page
fixed in
ACC v7: 7.4.4 build 9401
severity
10 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
assigned by
adobe
published
2026-08-25

check us helpx.adobe.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
28 Aug 20260.00616
31 Aug 20260.00676
28 Sep 20260.01279

3 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: ACC v7: 7.4.4 build 9401. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-76193', '2026-10-30T23:59:59.999999Z', now());