Skip to content
Notion·

🔐Notion Cuts Ties With Fireworks After Incident Exposes Under 1% of Workspaces

Check your Notion AI chats and rotate those secrets

TL;DR

Notion cut all ties with Fireworks AI after a security incident exposed some unattributable Notion AI chat sessions. Fewer than 1% of workspaces may be affected. If you pasted credentials into Notion AI recently, rotate them now.

Notion just pulled the plug on Fireworks AI. Fewer than 1% of workspaces may have had unattributable Notion AI chat sessions exposed in a security incident at Fireworks, and Notion has disconnected, deleted its data from Fireworks, and halted all training runs. If you use Notion AI or build on it, this is your cue to check. Notion's Insights feature is disabled while it investigates. Workspace owners can open the sidebar, click ?, and find Security incident review. The catch? The chats aren't labeled with who wrote them or which workspace they came from, so affected members may need to check their own data. The transcripts didn't include tool call results, and no other workspace data is affected. Enterprise owners get a CSV and an annotated CSV with extra metadata. Everyone else gets a shareable link for affected members. Notion also recommends rotating passwords, API keys, and other credentials pasted into Notion AI during the affected window. Fireworks serves tens of thousands of customers, so this isn't a tiny vendor problem.

Notion Cuts Ties With Fireworks After Incident Exposes Under 1% of Workspaces — Notion

Key Points

1

Fireworks powers tens of thousands of customers and is used by hundreds of thousands of developers, which makes this incident far wider than one vendor's trouble.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

NotionFireworks AIAI securitydata exposurecredential rotation

Comments

Subscribe to join the conversation...

Be the first to comment