Cyber Resilience

CVE-2026-22586

Exposed Creds in Salesforce Marketing Cloud Engagement ≤ 2026-01-21

Published
24 January 2026
Modified
15 May 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0061 46th percentile
Risk Priority 72 floored blend · peak EPSS

Summary

CVE-2026-22586 is a critical-severity Use of Hard-coded Cryptographic Key (CWE-321) vulnerability in Salesforce Marketing Cloud Engagement. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Private Keys (T1552.004); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-22586 is a hard-coded cryptographic key vulnerability (CWE-321) in Salesforce Marketing Cloud Engagement, specifically affecting the CloudPages, Forward to a Friend, Profile Center, Subscription Center, Unsub Center, and View As Webpage modules. This flaw enables Web Services Protocol Manipulation and impacts all versions of Marketing Cloud Engagement prior to January 21st, 2026. The vulnerability carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), classifying it as critical due to its severe potential impacts.

Unauthenticated attackers can exploit this vulnerability remotely over the network with low complexity and no requirement for user interaction or privileges. Successful exploitation allows adversaries to manipulate web services protocols, resulting in high confidentiality, integrity, and availability impacts on affected systems.

Salesforce has published a security advisory at https://help.salesforce.com/s/articleView?id=005299346&type=1, which addresses the issue. Mitigation requires updating to Marketing Cloud Engagement versions released on or after January 21st, 2026.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22585Same product: Salesforce Marketing Cloud Engagement
CVE-2026-22583Same product: Salesforce Marketing Cloud Engagement
CVE-2026-22582Same product: Salesforce Marketing Cloud Engagement
CVE-2025-49164Shared CWE-321
CVE-2025-26340Shared CWE-321
CVE-2025-62581Shared CWE-321
CVE-2026-34635Shared CWE-321
CVE-2026-5846Shared CWE-321
CVE-2025-54807Shared CWE-321
CVE-2025-63289Shared CWE-321

Affected Assets

salesforce
marketing cloud engagement
≤ 2026-01-21

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Requiring cryptographic keys to be established and managed according to defined requirements prevents developers from embedding static unchangeable keys.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-SDLC activities such as code review and secret scanning directly prevent embedding static keys.

PR.DS-01 partial match
prevents

Data-at-rest protection policies require proper key management and therefore discourage hard-coded keys.

PR.DS-02 partial match
prevents

Data-in-transit protection similarly depends on non-hard-coded keys for encryption.

PR.PS-01 partial match
prevents

Configuration baselines and reviews can prohibit hard-coded keys in deployed artifacts.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Key-management controls that govern generation, rotation and protection of keys make the use of embedded hard-coded cryptographic keys less likely and easier to detect.

References