Security readout for executives and security teams
Plain-English summary
Adobe Campaign Classic contains a critical authorization flaw that may let a remote, unauthenticated attacker run code without user interaction. Successful exploitation could compromise sensitive campaign data, alter operations, disrupt service, and affect connected systems under the application’s privileges.
Executive priority
Treat as an immediate remediation priority for confirmed affected deployments, especially externally reachable systems. The maximum CVSS score and unauthenticated, interaction-free code-execution potential create severe business risk. Escalate ownership, exposure verification, containment, patching, and post-remediation validation.
Technical view
CVE-2026-27302 is an incorrect authorization vulnerability (CWE-863) in Adobe Campaign Classic. The supplied CVSS 3.1 vector is 10.0: network-accessible, low complexity, no privileges or interaction required, changed scope, and high confidentiality, integrity, and availability impact. Code executes in the current user context.
Likely exposure
The supplied affected-version data identifies ACC v7 version 7.4.4 build 9400, but also contains an ambiguous “0” entry. Default status is unaffected, so do not assume every ACC release is vulnerable. Prioritize internet-reachable or externally accessible deployments and confirm exact builds against Adobe APSB26-123.
Exploitation context
The vulnerability is described as remotely exploitable without authentication or user interaction. The bundle does not include exploit details, proof-of-concept evidence, or confirmation of active exploitation. It is not identified as a CISA KEV entry in the supplied data.
Researcher notes
Authorization failure is the stated root cause, but the bundle provides no affected component, request path, attack primitive, indicators, or fixed version. The changed-scope rating suggests impact may cross a security boundary. Researchers should rely on Adobe APSB26-123 for authoritative version and remediation details.
Mitigation direction
- Review Adobe APSB26-123 and apply the vendor-specified update or mitigation promptly.
- Restrict network access to ACC until remediation is confirmed.
- Limit ACC service privileges and access to connected systems.
- Increase monitoring for unusual ACC activity and unauthorized changes.
Validation and detection
- Inventory all ACC instances and record their exact version and build.
- Compare each deployment against the affected and corrected versions in APSB26-123.
- Confirm external exposure, authentication boundaries, and network restrictions.
- Review ACC and surrounding system logs for suspicious execution or unauthorized changes.
- Verify remediation through approved configuration and version checks.
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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCVE-2026-27302 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-123.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.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.