← Blog

Notion Data Leak: Fireworks AI Vendor Chats (Nov 2026)

Share on X

November 9, 2026: Notion said a breach at its AI vendor Fireworks AI exposed Notion AI chat transcripts from fewer than 1% of Notion workspaces. Most of the transcripts carry no workspace, user or company label. Notion says its own systems were not breached. The incident is logged in the Notion breach record.

Notion used Fireworks AI for two jobs: classifying chats for its Insights feature, which shows customers how their teams use Notion AI, and running open-weight AI models. Fireworks told Notion on the evening of November 2, 2026 that a small dataset had been accessed. That first dataset contained only synthetic test data. By the morning of November 3, Notion had disconnected from Fireworks, deleted the data held there and stopped sending it traffic.

On November 6, Fireworks told Notion that attackers may also have reached customer data. Fireworks confirmed this on November 8. Notion published its security advisory on November 9 and updated it on November 10.

What happened in the Notion and Fireworks incident?

This is a vendor breach. The attacker reached Fireworks' environment, not Notion's. The data was already stored at Fireworks before Notion disconnected, which is why cutting the connection on November 3 did not prevent the later exposure.

Fireworks' own investigation widened in November to cover billing data and some customer model files. The Hacker News reported the wider scope, and our Fireworks AI breach post covers what the vendor itself disclosed.

Notion has turned off Insights while the investigation continues and no longer serves open-weight models through Fireworks. It says no other Notion features were affected.

What data was exposed?

The exposed dataset contained Notion AI chat transcripts used by Insights. For the vast majority of affected workspaces, the transcripts were not labeled with who wrote them or which workspace they came from, and they did not include tool-call results.

That lowers the risk but does not remove it. People often paste passwords, API keys or customer details into AI chats, and that text stays sensitive whether or not it carries a name. Notion advises affected customers to treat the data as exposed and to rotate any credentials they pasted into Notion AI.

The incident is separate from an unverified June 2026 claim that 110 million Notion records were for sale. That claim has never been confirmed.

Who is affected?

Notion has emailed the workspaces it identified, which make up fewer than 1% of all Notion workspaces. Those customers can review the affected chats inside their workspace using the instructions in the email.

If you have not heard from Notion, the company says your workspace has not been identified as affected and you do not need to do anything for now. The investigation is still open, so more customers could be contacted later. People who only use Notion pages, wikis or calendars and never used Notion AI are not in this dataset.

How does this fit with other AI vendor breaches?

The Fireworks breach came weeks after another infrastructure incident aimed at AI credentials. In late October, the cloud hosting platform Railway disclosed that attackers decrypted environment variables for up to 100,000 workspaces and ran up about $740,000 in fraudulent AI usage. The two incidents involve different companies and different data.

What should Notion users do?

  1. If Notion emailed you, follow the steps in that email to review the affected chats inside your workspace.
  2. Rotate any password, API key or token that anyone on your team pasted into Notion AI during the incident window.
  3. Treat the transcripts as exposed, even if they are not labeled with your workspace.
  4. Be wary of emails asking you to "restore Insights" or confirm payment details on a new website.
  5. If you were not contacted, no action is needed now, but watch for later updates to Notion's advisory.

Frequently asked questions

Was Notion hacked?

No. Notion says this was not a breach of its own systems. The attacker reached Fireworks AI, a vendor Notion used for its Insights feature and for running open-weight models. The exposed chat transcripts were stored at Fireworks, and Notion disconnected from the vendor on November 3.

How many Notion users were affected?

Notion says fewer than 1% of its workspaces were affected and has not published a number of people. Most of the exposed chat transcripts carry no workspace, user or company label. Notion has emailed the customers it identified with instructions for reviewing the data.

What should I do if Notion contacted me?

Review the affected chats inside your workspace using the steps in Notion's email. Then rotate any passwords, API keys or tokens that were pasted into Notion AI, because pasted secrets stay sensitive even when a transcript carries no name.

Is this related to the 110 million Notion records claim?

No. The June 2026 claim of 110 million Notion records was posted by an unknown seller and has never been confirmed. The Fireworks incident is a separate, confirmed vendor breach that Notion disclosed itself on November 9, 2026.