# Cloudflare (2025): what the sources say about the cloud incident

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Cloudflare disclosed the incident on 2 Sep 2025. What was exposed, as the sources state it: Salesforce case objects (customer support tickets and associated data: contact information, subject lines and case correspondence, not attachments); the company found 104 Cloudflare API tokens in the data.

- **Disclosed:** 2 Sep 2025
- **Incident window:** August 9 to 17, 2025
- **Cloud or provider:** Salesforce
- **What was exposed:** Salesforce case objects (customer support tickets and associated data: contact information, subject lines and case correspondence, not attachments); the company found 104 Cloudflare API tokens in the data
- **How access was gained:** The company stated the threat actor obtained OAuth credentials associated with the Salesloft Drift chat agent's Salesforce integration, and used a stolen credential used by the Salesloft integration to log in to its Salesforce tenant.
- **Access path:** [Third-party access](/access-paths/third-party-access/); also [Leaked access keys and secrets](/access-paths/leaked-access-key/)
- **Kind of control that addresses it:** restrict third-party integration tokens to approved source addresses, give them minimum scopes, and rotate them on a short schedule

## In the words of the source

“a threat actor breached their systems. As part of the breach, the threat actor was able to obtain OAuth credentials associated with the Salesloft Drift chat agent’s Salesforce integration” (company statement, [The impact of the Salesloft Drift breach on Cloudflare and our customers](https://blog.cloudflare.com/response-to-salesloft-drift-incident/))

## Primary sources

- company statement: [The impact of the Salesloft Drift breach on Cloudflare and our customers](https://blog.cloudflare.com/response-to-salesloft-drift-incident/), dated 2 Sep 2025

If a field is wrong or a newer primary source exists, [write to the editor](mailto:editor@cloudsecuritybreaches.com?subject=Correction%3A%20Cloudflare%20(cloudflare-salesforce-drift-2025)) with the entry name in the subject.

## Related pages

- [Nx (Nrwl) 2025: github actions](/incidents/nx-github-actions-2025/)
- [Salesloft (Drift) 2025: leaked access keys and secrets](/incidents/salesloft-drift-2025/)
- [Google 2025: salesforce instance](/incidents/google-salesforce-instance-2025/)

## Sources

- The impact of the Salesloft Drift breach on Cloudflare and our customers: https://blog.cloudflare.com/response-to-salesloft-drift-incident/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/incidents/cloudflare-salesforce-drift-2025/
