LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22586: Hard-coded Cryptographic Key vulnerability in Salesforce Marketing Cloud Engagement (CloudPages, Forward to...

Hard-coded Cryptographic Key vulnerability in Salesforce Marketing Cloud Engagement (CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, View As Webpage modules) allows Web Services Protocol Manipulation. This issue affects Marketing Cloud Engagement: before January 21st, 2026.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A critical Salesforce Marketing Cloud Engagement issue involved a hard-coded cryptographic key in several customer-facing modules. If exploitable, it could let unauthenticated attackers manipulate web services and affect confidentiality, integrity, and availability. Salesforce lists systems before January 21, 2026 as affected; provided sources do not show CISA KEV listing or active exploitation.

Executive priority

Treat as urgent for any organization using Salesforce Marketing Cloud Engagement. The issue is critical by CVSS and affects externally reachable marketing functions. Prioritize vendor confirmation of tenant remediation and focused review for suspicious activity.

Technical view

CVE-2026-22586 is a CWE-321 hard-coded cryptographic key vulnerability in Salesforce Marketing Cloud Engagement. Affected modules include CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, and View As Webpage. CVSS 3.1 is 9.8, with network access, low complexity, no privileges, and no user interaction.

Likely exposure

Organizations using Salesforce Marketing Cloud Engagement modules before January 21, 2026 may be exposed. Because this is a Salesforce cloud service, exposure confirmation likely depends on Salesforce tenant status, product usage, and vendor advisory details.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation could be possible. The supplied sources do not provide exploit details, proof-of-concept status, or evidence of active exploitation. CISA KEV status is false in the source bundle.

Researcher notes

Public detail is limited. The core issue is CWE-321 in Salesforce Marketing Cloud Engagement enabling web services protocol manipulation. Avoid assuming exploitability beyond the CVSS and vendor description. No public source in the bundle confirms active exploitation or provides a customer-applied patch procedure.

Mitigation direction

  • Review the Salesforce advisory and tenant notifications for CVE-2026-22586.
  • Confirm Marketing Cloud Engagement is in Salesforce's corrected post-January 21, 2026 state.
  • Inventory use of CloudPages and listed Marketing Cloud Engagement modules.
  • Open a Salesforce support case if tenant exposure or remediation status is unclear.

Validation and detection

  • Check whether your organization used affected modules before January 21, 2026.
  • Verify Salesforce confirms your tenant is no longer affected.
  • Review Marketing Cloud logs for unusual web service activity around affected modules.
  • Document Salesforce case responses and advisory status for audit evidence.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2026-22586 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-22586Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SalesforceMarketing Cloud Engagement0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-321 · source CWE mapping

Use of Hard-coded Cryptographic Key

Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.