Third-Party Security Incident Impacting Salesforce Integration via Drift

What to do

• Check whether your product depends on Cloudinary. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2025-09-03 13:06 UTC and 2025-09-03 13:06 UTC may need a replay.

• Subscribe to Cloudinary's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=cloudinary works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Cloudinary 1

1. resolvedSep 3, 2025, 1:06 PM UTC

   We have been informed of a security incident involving Drift, a third-party application previously integrated with our Salesforce environment as part of Cloudinary’s support processes. This incident is part of a broader issue affecting multiple organizations that use these services. Immediately upon learning of the situation, we disabled all connections between Cloudinary’s systems and Drift. We are actively working with Salesforce, Drift, and other relevant parties to support the ongoing investigation and to ensure the continued security of our data and systems. At this time, our review indicates that no data stored within Cloudinary’s products or core systems has been affected. The information involved appears limited to standard business contact details and certain support communications managed through Salesforce. Customers impacted by this incident have been notified directly with guidance and recommended next steps. As always, we encourage all customers to remain vigilant for any phishing or social engineering attempts that could result from incidents of this nature.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.