dbcve.org
Marketing Cloud EngagementApplication · Salesforce

CVE-2026-22585

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-24
Fix available
A fix is available. Upgrade to 2026-01-21 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Use of a broken or risky cryptographic algorithm in multiple Salesforce Marketing Cloud Engagement web modules (CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, View As Webpage) allows manipulation via web services protocol. The vulnerability stems from weak or improper cryptographic implementation in these user-facing components.

MitigationApply Salesforce's January 21st, 2026 patch/update to Marketing Cloud Engagement. If immediate patching is not possible, review and harden cryptographic implementations in the affected modules and consider restricting web services protocol access while awaiting the vendor fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Marketing Cloud EngagementApplication
Affected:< 2026-01-21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm you use Salesforce Marketing Cloud Engagement
    Verify your marketing automation platform is Salesforce Marketing Cloud Engagement (formerly ExactTarget). Check your Salesforce org or integration documentation for the product name.
    Affected if You do not use Salesforce Marketing Cloud Engagement, this CVE does not apply.
  2. Identify enabled web-facing modules
    Review which of these modules are enabled in your SFMC setup: CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, or View As Webpage. Check via Marketing Cloud admin settings or Cloud Page management interfaces.
    Affected if None of these modules are web-facing or enabled, the vulnerability surface is not exposed.
  3. Check your SFMC deployment version or release date
    Locate your Salesforce Marketing Cloud Engagement version or deployment date. This is typically found in Salesforce setup under 'Installed Packages', 'Account settings', or by contacting Salesforce support. Compare the date to January 21st, 2026.
    Affected if Your deployment version is dated before January 21st, 2026 and web-facing modules are enabled, you are likely affected.

You are affected if you use Salesforce Marketing Cloud Engagement with any web-facing modules (CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, View As Webpage) enabled, and your deployment version predates the January 21st, 2026 patch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026-01-21 or later
Fixed in 2026-01-21
Interim mitigation

Apply Salesforce's January 21st, 2026 patch/update to Marketing Cloud Engagement. If immediate patching is not possible, review and harden cryptographic implementations in the affected modules and consider restricting web services protocol access while awaiting the vendor fix.

Recommended fix High confidence

Marketing Cloud Engagement version 2026-01-21 or later

  1. 1. Identify the current version of Salesforce Marketing Cloud Engagement by checking the Help\u00a0>\u00a0About page or contacting Salesforce Support
  2. 2. Confirm the installed version is earlier than January 21, 2026
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Contact Salesforce Support or work with your Salesforce administrator to upgrade Marketing Cloud Engagement to version 2026-01-21 or later
  5. 5. After upgrade, verify that all affected modules (CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, View As Webpage) are functioning correctly
  6. 6. Validate that cryptographic operations in the affected modules are now using secure algorithms

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Marketing Cloud Engagement Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22585 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data