# Snyk: Third-Party Vendor Security Incident (Klue)

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-06-19 23:15 UTC · Resolved: 2026-07-08 15:26 UTC · Duration: 19 d
- Updates: 3 · Affected components: SNYK-EU-01 (app.eu.snyk.io) - Snyk Learn, Snyk Learn, Snyk IaC, SNYK-US-01 (app.snyk.io) - Snyk IaC, SNYK-GOV-01 (app.snykgov.io) - Snyk Open Source, Snyk Open Source, Snyk AppRisk, SNYK-AU-01 (app.au.snyk.io) - Snyk AppRisk, Snyk Open Source, SNYK-US-02 (app.us.snyk.io) - Snyk Open Source, SNYK-AU-01 (app.au.snyk.io) - Snyk Container, Snyk Container, Snyk Learn, SNYK-US-02 (app.us.snyk.io) - Snyk Learn, Evo by Snyk, SNYK-US-02 (app.us.snyk.io) - Evo by Snyk, SNYK-AU-01 (app.au.snyk.io) - Snyk Code, Snyk Code, Snyk IaC, SNYK-US-02 (app.us.snyk.io) - Snyk IaC, SNYK-AU-01 (app.au.snyk.io) - Snyk Learn, Snyk Learn, SNYK-EU-01 (app.eu.snyk.io) - Snyk IaC, Snyk IaC, Evo by Snyk, SNYK-US-01 (app.snyk.io) - Evo by Snyk, Snyk AppRisk, SNYK-EU-01 (app.eu.snyk.io) - Snyk AppRisk, Snyk Code, SNYK-EU-01 (app.eu.snyk.io) - Snyk Code, Snyk Learn, SNYK-US-01 (app.snyk.io) - Snyk Learn, Snyk Support (support.snyk.io) - Support Portal, Support Portal, SNYK-EU-01 (app.eu.snyk.io) - Snyk Open Source, Snyk Open Source, Snyk Container, SNYK-US-01 (app.snyk.io) - Snyk Container, Evo by Snyk, SNYK-AU-01 (app.au.snyk.io) - Evo by Snyk, Snyk Open Source, SNYK-US-01 (app.snyk.io) - Snyk Open Source, SNYK-AU-01 (app.au.snyk.io) - Snyk Open Source, Snyk Open Source, Snyk Container, SNYK-GOV-01 (app.snykgov.io) - Snyk Container, Snyk AppRisk, SNYK-US-01 (app.snyk.io) - Snyk AppRisk, SNYK-AU-01 (app.au.snyk.io) - Snyk IaC, Snyk IaC, Snyk Container, SNYK-EU-01 (app.eu.snyk.io) - Snyk Container, SNYK-GOV-01 (app.snykgov.io) - Snyk IaC, Snyk IaC, Snyk AppRisk, SNYK-US-02 (app.us.snyk.io) - Snyk AppRisk, Snyk Container, SNYK-US-02 (app.us.snyk.io) - Snyk Container, Evo by Snyk, SNYK-EU-01 (app.eu.snyk.io) - Evo by Snyk, Snyk Code, SNYK-US-02 (app.us.snyk.io) - Snyk Code, Snyk Code, SNYK-US-01 (app.snyk.io) - Snyk Code, Snyk Code, SNYK-GOV-01 (app.snykgov.io) - Snyk Code
- [Vendor status page: https://stspg.io/6wtd2kq8qbx1](https://stspg.io/6wtd2kq8qbx1)
- [Company: Snyk](https://rewindex.com/company/snyk.md)

## Timeline of updates

- **investigating** 2026-06-19 23:15 UTC: We were notified of a security incident involving Klue, a market intelligence platform used by Snyk and a wide range of companies for competitive intelligence. An unauthorized party accessed data from Snyk's Salesforce environment through Klue's integration.  Other security vendors, such as Recorded Future (https://www.recordedfuture.com/blog/klue-security-incident), Tanium (https://www.tanium.com/blog/security-update-taniums-response-to-the-klue-breach-that-allowed-data-exfiltration-from-salesforce/), Huntress (https://www.huntress.com/blog/klue-breach-investigation), and Jamf (https://www.jamf.com/blog/klue-incident/) have been impacted and have shared updates publicly.  Our investigation shows that, to our knowledge at this point in time, the impact was primarily limited to business data fields within the Salesforce environments. This includes customer business contact information and only the title and description from a limited subset of customer support cases. The body or contents of the support cases were not included nor did it affect Snyk's products. There was no impact on our ability to serve our customers. Snyk's platform, services, and infrastructure remain fully operational and were not involved. Upon notification from Klue, we promptly disabled the Klue integration in Salesforce and began our own review. We will post updates here as we learn more.
- **monitoring** 2026-06-22 22:12 UTC: We were notified of a security incident involving Klue, a market intelligence platform used by Snyk and a wide range of companies for competitive intelligence. An unauthorized party accessed data from Snyk's Salesforce environment through Klue's integration.  Other security vendors, such as Recorded Future, Tanium, Huntress, and Jamf have been impacted and have shared updates publicly.  Our investigation shows that, to our knowledge at this point in time, the impact was primarily limited to business data fields within the Salesforce environments. This includes customer business contact information and only the title and description from a limited subset of customer support cases. The body or contents of the support cases were not included nor did it affect Snyk's products. There was no impact on our ability to serve our customers. Snyk's platform, services, and infrastructure remain fully operational and were not involved. Upon notification from Klue, we promptly disabled the Klue integration in Salesforce and began our own review. We will post updates here as we learn more.
- **resolved** 2026-07-08 15:26 UTC: Our forensic investigation into the June 2026 Klue/Salesforce incident, conducted in partnership with Mandiant, is now complete. The investigation confirmed that the impact was limited to business CRM data. No evidence of impact to the Snyk platform, and any sensitive data within, was found. All impacted customers were notified directly and the data involved is consistent with what was disclosed in our June 22 blog post (https://snyk.io/blog/when-a-vendors-breach-becomes-yours-lessons-from-the-klue-incident/).


---
Canonical: https://rewindex.com/company/snyk/incidents/3gw3m2ppwbp3 · Markdown: https://rewindex.com/company/snyk/incidents/3gw3m2ppwbp3.md · JSON: https://rewindex.com/api/v1/companies/snyk/incidents/3gw3m2ppwbp3 · Generated 2026-10-18T09:40:43.449Z