Protocol manipulation via risky link cryptography
Published Jan 24, 2026 · Updated Jan 24, 2026
Broken cryptography in Salesforce Marketing Cloud Engagement before January 21, 2026 allows remote attackers to manipulate web protocols. The affected link-generation modules used an undisclosed broken or risky cryptographic algorithm; Salesforce disclosed only that AES-GCM replaced it. Unauthenticated network access is sufficient, but Salesforce has not detailed the manipulated fields or the resulting data or service effects.
Summary
What happened
Broken cryptography in Salesforce Marketing Cloud Engagement before January 21, 2026 allows remote attackers to manipulate web protocols. The affected link-generation modules used an undisclosed broken or risky cryptographic algorithm; Salesforce disclosed only that AES-GCM replaced it. Unauthenticated network access is sufficient, but Salesforce has not detailed the manipulated fields or the resulting data or service effects.
The record
- CVE
- CVE-2026-22585
- Published
- Jan 24, 2026
- Updated
- Jan 24, 2026
- Vendor
- Salesforce
- Product
- Marketing Cloud Engagement
- Classifications
- CWE-327, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2026CVE publishedPublication date reported by the CVE source.
- Jan 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <January 21, 2026
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo