LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22585: Use of a Broken or Risky Cryptographic Algorithm vulnerability in Salesforce Marketing Cloud Engagement (Cl...

Use of a Broken or Risky Cryptographic Algorithm 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

Salesforce disclosed a critical cryptographic weakness in Marketing Cloud Engagement affecting several customer-facing modules before January 21, 2026. The CVE rates it as remotely exploitable without authentication or user interaction. The provided sources do not state active exploitation or customer-applied patch details.

Executive priority

High priority for organizations using Salesforce Marketing Cloud Engagement. Assign the application owner to confirm exposure and Salesforce remediation status. If the named modules were used before January 21, 2026, treat this as an urgent third-party SaaS risk review.

Technical view

CVE-2026-22585 is CWE-327 in Salesforce Marketing Cloud Engagement modules: CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, and View As Webpage. It allows Web Services Protocol Manipulation. CVSS 3.1 is 9.8: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Likely exposure

Exposure is likely limited to organizations using Salesforce Marketing Cloud Engagement and the named modules before January 21, 2026. The CVE record lists default status as unaffected but describes the product as affected before that date, so tenant-specific confirmation is important.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source states in-the-wild exploitation. However, the CVSS vector indicates a network-reachable, low-complexity issue requiring no privileges or user interaction, with potential high confidentiality, integrity, and availability impact.

Researcher notes

Public evidence is sparse. The CVE identifies the weakness class, affected Salesforce modules, date boundary, and CVSS vector, but does not provide technical root cause, proof of exploitation, indicators, or explicit customer-side fixes in the supplied sources.

Mitigation direction

  • Review the Salesforce advisory for CVE-2026-22585 and any tenant-specific instructions.
  • Confirm Marketing Cloud Engagement is no longer in the pre-January 21, 2026 affected state.
  • Inventory use of CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, and View As Webpage.
  • Monitor Salesforce support, Trust, or advisory updates for remediation confirmation and follow-up actions.
  • Review available security logs for anomalous web service protocol behavior.

Validation and detection

  • Verify whether your organization used Marketing Cloud Engagement before January 21, 2026.
  • Check whether the named modules were enabled or externally reachable.
  • Compare Salesforce advisory guidance with internal tenant and module inventory.
  • Document Salesforce support or advisory confirmation for audit evidence.
  • Monitor CVE and KEV feeds for any exploitation-status changes.
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-327: 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-22585 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-22585Attack 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-327 · source CWE mapping

Use of a Broken or Risky Cryptographic Algorithm

Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.