On November 10, 2026, Notion published an advisory about a security incident at Fireworks AI, a company it used to run classification jobs for a feature called Insights and to serve some open-weight models. Notion says the incident affects fewer than 1% of workspaces. The data involved is Notion AI chat transcripts used for Insights. Notion says that for the vast majority of impacted workspaces those chats were “unattributable”: they were not labeled with who wrote them or which workspace they came from, and they did not contain tool-call results.
The practical point is wider than one product. Anything you type into an AI chat can end up with that tool’s own vendors. Keep passwords and API keys out of chat windows, share them through a password manager, and change any you have pasted. A short one-page AI use rule can make that a team habit rather than a reminder you send after the fact.
What happened
On the evening of November 2, Fireworks notified Notion that a small set of data had been accessed by malicious actors. Notion says that dataset included Notion AI synthetic testing data, and that no Notion AI customer data was involved at that stage. By the morning of November 3, Notion says it had disconnected its systems from Fireworks and stopped all communication with it. On November 4, Notion says it deleted all its data in the Fireworks system.
On November 6, Fireworks notified Notion that malicious actors may have accessed potential customer data. Notion began another investigation. On November 8, Fireworks confirmed the final impacted dataset. On November 9, Notion reached out to impacted customers.
After reviewing the November 8 dataset, Notion says it included Notion AI chat transcripts used for the Insights feature. For the vast majority of impacted workspaces, Notion says, those chats were unattributable: they were not labeled with a user or a workspace, and they did not contain tool-call results. Notion says no other Notion features were affected, and that this was not a breach of Notion’s own systems.
The Insights feature has been disabled while Notion investigates, and Notion is no longer serving open-weight models through Fireworks. On November 11, Notion added an update: it had revoked exposed Notion API keys that were found in affected user messages during its investigation. On November 12, Notion says it reported exposed third-party API keys found in those messages to the vendors that issued them. The advisory was first published November 10. Notion also made a style and clarity update that same day, and said no previously reported facts had changed.
Who is affected, and what to do
Notion says it has contacted customers whose workspaces were affected. If you have not heard from Notion, it says it has not identified your workspace as affected, and no action is needed right now. The investigation is ongoing, and Notion says it will contact you directly if that changes.
If Notion has contacted you, follow the instructions in that email. Notion says affected customers can retrieve and review the impacted data securely inside their workspace, and it recommends treating that data as if it were exposed. If anyone in an affected workspace pasted sensitive information, passwords, API keys or other credentials into Notion AI during the timeframe of the incident, rotate them.
Going forward, treat an AI chat window the same way you would treat an email to a vendor: useful for work, not a place for secrets. Share logins through a password manager, not by pasting them into a prompt.
If you want a simple plan for moving shared logins into a password manager, our $19 Password Manager Rollout Kit has a two-week plan, checklists, a staff email, a one-page policy and a tracker.
Updated November 14, 2026, to match Notion’s later timeline: the disconnect was November 3, the data deletion was November 4, and on November 12 Notion reported exposed third-party API keys to the vendors that issued them.
Sources
- Notion, “Fireworks AI incident”, originally published November 10, 2026; style and clarity update November 10, 2026; November 11, 2026 update on revocation of exposed Notion API keys found in affected user messages; November 12, 2026 timeline update and notice that Notion reported exposed third-party API keys found in affected user messages to the vendors that issued them (posted in the advisory’s updates on November 13, 2026). The updated advisory says Notion disconnected from Fireworks and stopped communication by the morning of November 3, and deleted all its data in the Fireworks system on November 4. The advisory says the incident affects fewer than 1% of workspaces; the exposed data is Insights chat transcripts, unattributable for the vast majority of impacted workspaces; Insights has been disabled and Notion is no longer serving open-weight models through Fireworks; affected customers should treat the data as exposed and rotate credentials pasted into Notion AI; customers Notion has not contacted need to take no action right now.
Related: A one-page AI use rule and Security and vulnerabilities, every security briefing, guide and tool in one place.
Follow Circuit & Capital on Bluesky, Facebook and X (@circuitsfit) for new briefings.