People search Gong data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Gong-linked incident (1 company-confirmed). This page maps every attested event through 2026 with internal links to canonical records.
Why Gong breach history matters
Gong operates in Energy (United States). Across indexed rows, recurring themes include third-party and supply-chain exposure, unverified actor or scraping claims. 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; licensed user data accessed via integration
Verified breach. Downstream Klue supply-chain victim — June 2026. Gong's Office of the CISO disclosed June 19 that Klue notified Gong of unauthorized access to its integration service; Gong confirmed a subset of customers using the Klue–Gong integration may have had licensed user data (names, business titles, emails) accessed based on Klue-provided suspicious IPs. Gong found no direct impact to call recordings or transcripts; revoked Klue tokens, blocked Klue API requests, and reached out to affected customers. Huntress separately Exposed categories include Subset of Klue-integration customers: internal licensed user names, business titles, and business emails—no call recordings, customer transcripts, or direct Gong product breach per. No attested victim count is published for this row yet. See the gong-klue-salesforce 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple Gong catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple Gong 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 Gong company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/gong · Latest: gong-klue-salesforce2026.
Sources: BreachHistory catalog (1 row for Gong), company and regulator disclosures cited in individual breach records.