Skip to content

Supabase's October 30 change: new public tables need a grant for Data API access. What to doSupabase's October 30 change is live: new public tables need a grant for Data API access. What broke and how to fix it

24 tools · 139 fixes · 42 issue guides · Sources: Supabase, GitHub, postgresql.org, Vercel + 53

Incident feed

Notion AI chats in Fireworks breach: what to do

Notion says the security incident at its AI vendor Fireworks AI affected fewer than 1% of Notion workspaces. A dataset Fireworks confirmed on November 8 included Notion AI chat transcripts used for Notion's Insights feature, which for the vast majority of affected workspaces were not labeled with who wrote them or which workspace they came from. Notion contacted affected customers on November 9, disabled Insights, stopped serving open-weight models through Fireworks, and recommends rotating any passwords, API keys, or other credentials pasted into Notion AI during the incident period. The advisory page says it was updated November 10, 2026, for style and clarity, with no changes to previously reported facts.

Share link · Share on X

Information disclosureLeaked keys

What was reported

Am I affected: Notion says the Fireworks incident is impacting fewer than 1% of workspaces. If Notion has not contacted you, Notion says it has not identified your workspace as affected and that no action is needed right now.

Do now: If Notion contacted you, review the chats it lets you retrieve and rotate any passwords, API keys, or other credentials you pasted into Notion AI during the incident timeframe.

Notion's security advisory, updated November 10, 2026, says the recent security incident at Fireworks AI, one of its AI vendors, is impacting fewer than 1% of Notion workspaces. Fireworks published its own incident update on November 9. The advisory page says "Updated version: November 10, 2026" and that on November 10 Notion updated the post for style and clarity, with no changes to previously reported facts.

What Notion says happened

  • November 2: Fireworks notified Notion that a small set of data had been accessed. Notion says that dataset included Notion AI synthetic testing data and no customer data.
  • November 3: Notion disconnected its systems from Fireworks, deleted all data in the Fireworks system, and stopped all communication between its systems and Fireworks.
  • November 6: Fireworks notified Notion that potential customer data may have been accessed, and Notion began another investigation.
  • November 8: Fireworks confirmed the final impacted dataset.
  • November 9: Notion reached out to impacted customers.

Notion says the dataset included Notion AI chat transcripts used for its Insights feature, and that for the vast majority of impacted workspaces the transcripts were unattributable: not labeled with who wrote them or which workspace they came from, and without tool call results. It says that beyond what is in the chat transcript itself, there is no information tying a chat back to workspaces, users, or companies, and that no other Notion features were affected.

Notion says it used Fireworks for classification jobs behind Insights and as a general inference provider for open-weight models in its product. Insights is disabled while it investigates, and it is no longer serving open-weight models through Fireworks.

What Notion recommends

Notion says affected customers can retrieve and review the impacted data inside their workspace, with instructions sent by email, and should treat that data as exposed. It recommends that affected customers rotate any passwords, API keys, or other credentials pasted into Notion AI during the incident timeframe. Notion says customers it has not contacted have not been identified as affected and need no action right now, and that its investigation is ongoing.

How to prevent it

If Notion told you your workspace was affected, search the exposed chats it lets you review for any key, token, or password, then revoke it at the service that issued it. Our advice, not Notion's: deleting the chat does not cancel the key. Going forward, keep secrets out of AI chats and docs. They can be stored and processed by vendors you never signed up with.

Sources

Related

The weekly fix

The weekly fix: 3 real security mistakes in vibe-coded apps and how to fix them, every Tuesday.

One email, every Tuesday. A welcome note follows the first signup.