Notion AI Chats Exposed in Fireworks Breach. How to Check Your Workspace
A breach at AI infrastructure provider Fireworks exposed some Notion AI chat transcripts, according to Notion. The company says fewer than 1% of its workspaces were affected. In a November 13 update, Notion said it had alerted outside vendors the previous day about API keys found in affected messages. If your workspace received a notice, open Notion directly to review what was exposed.
What happened and when
Fireworks says an attacker reached its development machines on October 24 through a compromised cloud provider. Notion disconnected from Fireworks on November 3, confirmed the scope of the customer dataset with the vendor on November 8 and began notifying affected customers on November 9. Notion says the transcripts had been used for Insights, a tool that helped workspace admins understand AI usage. Notion has disabled Insights while it investigates. The advisory defines the affected group by workspace and gives no country-by-country breakdown.
What the transcripts could reveal
Notion says most affected transcripts lacked the automatic labels that identify the user or workspace. The text itself can still identify someone. A prompt might contain a customer name or an API key, and an AI reply might quote part of a private page. Notion says the data included the text of prompts and replies, which in some cases could include selected text from a page. The company says attachments and the rest of a page were outside that scope.
There is a distinction between generating an answer and analyzing past chats. Notion says Fireworks had agreed to retain no data from the endpoints Notion used, but its investigation found that the endpoints had retained data. Insights was the feature that sent stored chats for analysis.
How to review an affected workspace
- Sign in to Notion directly, switch to the relevant workspace, then open ? in the sidebar and select Security incident review. Notion says workspace owners and affected members can use this screen to download the relevant data.
- Start with credentials in the conversation text. Revoke or replace exposed API keys and tokens at the service that issued them, and change any exposed passwords. If you use those keys in integrations, update the integrations to use the replacements.
- Check for names, email addresses, customer details and excerpts of internal work. If this is a work account, share the findings through your organization’s security process and keep the downloaded files in a restricted location.
If you did not receive a notice
Check with your workspace owner first. Notion says workspaces whose owners and members have received no notice have no action to take at this time. Its investigation is ongoing, and it says it will contact newly identified customers. For anyone who did receive a notice, the next step is to review the affected transcript text. Notion revoked exposed keys it had issued on November 11. If an affected chat contains a key from another service, follow that service’s instructions to replace it.
Sources · Notion’s security advisory and November 13 update · Notion’s workspace review instructions · Fireworks AI’s incident bulletin · TechCrunch’s reporting · BleepingComputer’s coverage
Comments
Post a Comment