Security readout for executives and security teams
Plain-English summary
A critical Adobe Campaign Classic flaw may let an unauthenticated remote attacker make the server access unintended resources and ultimately run code. Successful exploitation could compromise sensitive campaign data, alter systems, or disrupt service without user action. The supplied version information is ambiguous, so organizations should confirm affected builds directly with Adobe.
Executive priority
Treat this as an immediate remediation priority where affected ACC systems are externally reachable or handle sensitive data. Assign ownership, confirm build exposure, and follow Adobe’s current guidance. If build status remains uncertain, apply interim access controls and escalate to Adobe support rather than assuming the deployment is unaffected.
Technical view
CVE-2026-76193 is an SSRF vulnerability classified as CWE-918. Its CVSS 3.1 score is 10.0: network-accessible, low complexity, no privileges or interaction required, changed scope, and high confidentiality, integrity, and availability impact. The description states SSRF could lead to arbitrary code execution in the current-user context.
Likely exposure
The bundle identifies Adobe Campaign Classic v7, including 7.4.4 build 9401, but also contains an unexplained version value of “0” and defaults other versions to unaffected. Internet-accessible or otherwise untrusted-network-reachable deployments merit immediate review. Confirm exact affected builds through Adobe’s advisory.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. Nevertheless, its unauthenticated network attack path, low complexity, lack of user interaction, and code-execution consequence create substantial exploitation potential. No exploit procedure or proof of concept is included.
Researcher notes
The impact chain is SSRF to arbitrary code execution, but the supplied bundle provides no intermediate technical details. The affected-version data is internally unclear because it lists “0” alongside ACC v7 7.4.4 build 9401. Validate scope against APSB26-134. Do not infer active exploitation, additional products, affected versions, or a specific patch from this evidence.
Mitigation direction
- Check Adobe’s advisory for the remediation applicable to your exact ACC version and build.
- Prioritize vendor-recommended remediation for externally reachable or business-critical ACC deployments.
- Restrict untrusted network access to ACC while remediation is pending.
- Limit ACC server outbound access to required destinations as an interim SSRF risk reduction.
Validation and detection
- Inventory all Adobe Campaign Classic instances, versions, builds, and network exposure.
- Compare each deployment against the exact affected-build information in Adobe’s advisory.
- Verify remediation status using Adobe’s prescribed version or build checks.
- Review ACC and network telemetry for unexpected outbound requests or unexplained process activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-76193 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96adobeVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://helpx.adobe.com/security/products/campaign/apsb26-134.htmlCVE reference, adobe · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.