People search Jamf data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Jamf-linked incident (1 company-confirmed). This page maps every attested event through 2026 with internal links to canonical records.
Why Jamf breach history matters
Jamf operates in Government (United States). Across indexed rows, recurring themes include third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — Klue OAuth supply-chain breach; Salesforce instance data accessed
Verified breach. Downstream Klue supply-chain victim — June 2026. Jamf disclosed June 18 that an unauthorized party accessed Jamf's Salesforce instance data through Klue's integration after Klue's environment was compromised. Jamf immediately disabled the Klue Salesforce integration, engaged forensic experts and law enforcement, and reported no evidence of lateral movement or impact to Jamf products/Apple device management services. Customer communication warned of possible phishing impersonating Jamf employees using Salesforce con Exposed categories include Primarily business data fields within Jamf Salesforce environment per ongoing investigation—no impact to Jamf products or customer service delivery; phishing risk from exposed CRM . No attested victim count is published for this row yet. See the jamf-klue-salesforce 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple Jamf catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the Jamf company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/jamf · Latest: jamf-klue-salesforce2026.
Sources: BreachHistory catalog (1 row for Jamf), company and regulator disclosures cited in individual breach records.