Notion says Fireworks breach exposed customer AI chat transcripts
Notion disclosed that a security breach at Fireworks AI, its AI infrastructure provider, exposed Notion AI chat transcripts in a small number of workspaces — less than 1% of its users, according to the company. The transcripts came from the Insights feature, and the attacker also compromised metadata, billing information, model weights and datasets. It is Fireworks' second breach in weeks.
Incident timeline
According to BleepingComputer (November 11, 2026), the attacker accessed Fireworks AI's development environment on October 23 via a third-party cloud provider. On November 2, Notion received an alert from Fireworks about an exposed dataset that, the vendor said, contained only synthetic test data; the company responded by cutting off traffic to Fireworks, deleting all its data from the vendor's systems and halting training runs by November 3. On November 8, Fireworks confirmed that real customer data had been accessed — including that of Notion users.
"Upon analysis of the dataset Fireworks AI gave us on November 8, we discovered that it included Notion AI chat transcripts used for the Insights feature, which for the vast majority of impacted workspaces were unattributable," Notion said in its update. "Unattributable means the chats weren't labeled with who wrote them or which workspace they came from, and the transcripts did not contain tool call results." The Insights dataset has since been disabled.
Notion also published an incident FAQ noting that Fireworks had contractually committed to zero data retention for Notion data.
What affected users should do
Owners of potentially affected workspaces can review the data through "Security incident review" in Notion's desktop web interface and share a link with members to download their own transcripts. The key recommendation: **rotate any passwords, API keys or other credentials entered into affected chats**. If neither a user nor their workspace owner received a notice, Notion says no action is needed — they are most likely not part of the impacted subset.
Closing
Third-party risk in the AI stack in its purest form: not even a contractual zero-retention clause kept customer chats and model weights out of reach when the vendor itself was breached. The question every team should ask its AI provider this week: where does our data live, who processes it, and what happens when *they* become the target?
--- **Primary source:** BleepingComputer — "Notion says Fireworks breach exposed customer AI chat transcripts", 2026-11-11. https://www.bleepingcomputer.com/news/security/notion-says-fireworks-breach-exposed-customer-ai-chat-transcripts/ (HTTP 200 verified 2026-11-12; Argos batch 1). **Cited within the source:** Notion's official statement and incident FAQ; Fireworks AI confirmations. **Category:** Cybersecurity · **Topics:** Notion, Fireworks AI, AI supply chain, transcripts, model weights. **Verification status:** facts and timeline taken from the verified primary article and Notion's statement cited within it; the exact scope of accessed data remains under investigation.