Incident · 8-K Item 1.05
8x8 reports Salesforce data taken through a compromised Klue integration
Compiled from public records. Updated 2026-11-15. By the cisonews.net Desk.
8x8, Inc. disclosed in a Form 8-K dated June 23, 2026 under Item 1.05 that an unauthorized party exploited a Klue Labs integration tied to its Salesforce customer relationship management system and took information about current, former and prospective customers. The material included contract and opportunity fragments, sales team notes and customer contact details, and the filing does not give a count of affected people or records. Klue has since said the attacker came in through a compromised legacy credential and used it to obtain the OAuth tokens that connect Klue to Salesforce, and 8x8 was one of several companies whose Salesforce data was reached that way.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened and when
8x8 says it learned of the problem on June 13, 2026. The company says the unauthorized access took place on June 11 and 12, 2026.
The filing says 8x8 and Klue, with support from Salesforce, acted on discovery. It adds that its investigation to date points to a contained scope.
What information was involved
The company describes the taken data as competitively sensitive and tied to customers rather than to employees. The listed items are fragmented contract and opportunity information, sales team notes, and contact information.
Effect on operations and finances
8x8 reports no business disruption beyond its own response work. It filed under Item 1.05 because of what was accessed, and it does not expect a material financial effect.
What 8x8's later filings say about the Klue incident
Nothing so far. 8x8 has filed two quarterly reports since the June 23, 2026 8-K, and neither names Klue, Salesforce or the incident. The first covers the quarter ended June 30, 2026, which includes the June 11 and 12 access dates. The second covers the quarter ended September 30, 2026. There is no 8-K/A either, so the open questions from June (whether customers were told one by one, who the actor was, how many records were taken) have no answer in the record.
| Filed | Filing | Mentions the incident |
|---|---|---|
| June 23, 2026 | Form 8-K, Item 1.05 | Yes: the original disclosure |
| August 5, 2026 | Form 10-Q, quarter ended June 30, 2026 | No |
| November 5, 2026 | Form 10-Q, quarter ended September 30, 2026 | No |
That silence fits what the 8-K itself said: 8x8 expected no material financial effect and filed because of what was taken, not because of cost or disruption. The guide to what later 10-Q and 10-K filings report shows that 28 of the 56 Item 1.05 incidents in this log have only that first 8-K on record.
How did the attacker get into 8x8's Salesforce through Klue?
Through Klue's own systems, not 8x8's. Klue, a competitive intelligence platform, said on June 18, 2026 that it had found unauthorized activity in part of its integration infrastructure on June 12. Its investigation found that the attacker got in with a compromised legacy credential tied to an integration service, and used that access to obtain the OAuth tokens that connect Klue to platforms such as Salesforce. With those tokens the attacker read data inside a number of connected customer environments.
Klue said it revoked the affected credentials and tokens, removed unauthorized code, disabled integrations that might be affected, notified law enforcement and engaged CrowdStrike. It said it had found no evidence that customer content stored in the Klue platform itself was affected. So the 8x8 data was taken from 8x8's Salesforce, by way of a token Klue held, which is why the 8-K names both Klue and Salesforce.
Which other companies were hit by the Klue incident?
8x8 is the only company to describe the incident in an SEC filing: a full-text search of EDGAR for "Klue" from May to November 2026 returns the 8x8 8-K and no other incident disclosure. Other affected companies posted their own notices. OneTrust said a threat actor used the compromised Klue Battlecards app to obtain OAuth tokens and then reached CRM data in Salesforce environments. OneTrust said it found the activity in its own Salesforce environment on June 17, 2026.
The two companies' own accounts line up on the window and the kind of data, and differ on what came next:
| 8x8 | OneTrust | |
|---|---|---|
| Where it said so | Form 8-K, Item 1.05, June 23, 2026 | Its blog, updates June 19 to August 27, 2026 |
| Access window | June 11 and 12, 2026 | June 11 to 12, 2026 (as Salesforce told it) |
| Data named | Contract and opportunity fragments, sales team notes, contact information | Business contact and CRM data, deal amounts, lost-deal comments, billing and shipping addresses, support email records |
| Individual notice | Not stated in any filing | All required notices to regulators and data subjects issued by August 27, 2026 |
OneTrust's list of fields is the most detailed public account of what a Klue-connected Salesforce instance held: company, name, email, phone number, title, website, industry, region, deal amount, lost comments, lead source, customer type, and billing and shipping addresses. By August 27, 2026, OneTrust said it had issued every required notification to regulators and to the people whose data was involved. 8x8 has said nothing comparable in the record. For how other vendor and cloud-tenant compromises show up in filings, see vendor and cloud-tenant breaches in 8-K filings.
What should an 8x8 customer or contact watch for?
Phishing that uses real deal details. The data taken from these Salesforce instances is the kind that makes a fake invoice or a fake renewal email look genuine: names, titles, phone numbers and notes on what was being negotiated. OneTrust told its customers to watch for unexpected messages that mention it and to check any request before answering it. The same advice fits a message that claims to come from 8x8: confirm it through a contact you already have, not one the message gives you.
Did 8x8 notify customers about the Klue breach?
The SEC filings do not say. The June 23, 2026 8-K said regulators were being notified, but it did not state whether affected customers would get individual letters, and the two later 10-Qs are silent on the incident.
What the filing leaves open
The investigation was still running when the filing was made. Regulators were being notified at that point. The filing also says additional security measures are being added, but it does not describe them. It does not state whether affected customers will receive individual letters, nor does it identify the threat actor or give a number of customer records involved.
How this disclosure's timing compares
8x8 disclosed 10 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.
The rule behind an Item 1.05 filing
Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other technology incidents on cisonews.net
- DreamHost, Breach notice, first disclosed November 2, 2026
- Photon Health, Breach notice, first disclosed October 28, 2026; affected: approximately 1706 Rhode Island residents
- Indico Data Solutions, Breach notice, first disclosed October 27, 2026; affected: 79 Rhode Island residents
- Stitch Connect Inc, Breach notice, first disclosed September 21, 2026; affected: 113,727 people in total (Indiana AG record)
- IDScan.net, Breach notice, first disclosed September 18, 2026; 27,624 affected in total (Indiana Attorney General)
Sources
- 2026-06-23 · A8x8, Inc., Form 8-K (SEC EDGAR), published June 23, 2026
- 2026-08-05 · A8x8, Inc., Form 10-Q for the quarter ended June 30, 2026 (SEC EDGAR), published August 5, 2026
- 2026-11-05 · A8x8, Inc., Form 10-Q for the quarter ended September 30, 2026 (SEC EDGAR), published November 5, 2026
- 2026-06-18 · AKlue Labs, An Update on the Recent Klue Security Incident, published June 18, 2026
- 2026-08-27 · AOneTrust, Update from OneTrust on Klue-Salesforce Security Incident, published August 27, 2026
- 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.