Security readout for executives and security teams
Plain-English summary
Adobe Campaign Classic contains a critical flaw that may let a low-privileged attacker run code under the compromised user’s authority. No user interaction is required. Successful exploitation could expose or alter sensitive campaign and customer data, although the supplied CVSS assessment does not indicate a direct availability impact.
Executive priority
Treat as an urgent remediation item because compromise could permit code execution and high-impact data exposure or alteration across a changed security scope. Establish ownership immediately, identify deployments, consult Adobe’s bulletin, and track remediation. Escalate internet-accessible or customer-data-processing instances first.
Technical view
CVE-2026-48317 is a CWE-95 eval-injection vulnerability. The CVSS 3.1 vector indicates network access, low complexity, low privileges, no user interaction, changed scope, and high confidentiality and integrity impact. The source bundle identifies ACC v7 7.4.3 build 9399, but its additional version value "0" is ambiguous.
Likely exposure
Organizations operating Adobe Campaign Classic should investigate immediately, particularly deployments of ACC v7 7.4.3 build 9399. The supplied data marks unspecified versions as unaffected, but does not provide a sufficiently clear affected-version range or deployment prerequisites. Internet or broadly network-accessible instances present greater practical exposure.
Exploitation context
The vulnerability can reportedly be exploited remotely by a low-privileged attacker without user interaction. The bundle does not identify public exploit code, observed attacks, or CISA KEV listing. KEV is explicitly false, so active exploitation should not be claimed; absence from KEV does not prove exploitation is not occurring.
Researcher notes
The supplied record supports arbitrary code execution in the current user context but provides no vulnerable component, attack primitive, indicators, exploit evidence, or named fixed build. The version entry "0" is unclear. Researchers and vulnerability managers should rely on APSB26-120 for precise applicability and remediation rather than extrapolating beyond the record.
Mitigation direction
- Inventory Adobe Campaign Classic deployments and record their exact versions and build numbers.
- Check Adobe bulletin APSB26-120 for the authoritative affected range and remediation instructions.
- Apply Adobe’s prescribed update or mitigation after appropriate operational testing.
- Restrict unnecessary network access to ACC while remediation status is being confirmed.
- Review and minimize privileges assigned to ACC users and service identities.
Validation and detection
- Verify each ACC instance’s version and build against Adobe bulletin APSB26-120.
- Confirm the vendor-prescribed remediation is present on every affected deployment.
- Test that unnecessary external and internal network paths to ACC are blocked.
- Review relevant authentication and application logs for unusual low-privileged account activity.
- Confirm ACC accounts retain only permissions required for their business functions.
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-95: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-48317 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
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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:L/UI:N/S:C/C:H/I:H/A:N3.15.8adobeVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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-120.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.
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.