Blackbox Blast
BB Preflight
← Incident log

CASE · Critical · other

Unverified reportCollected from public reports

Breach at vendor Fireworks AI may have exposed Notion AI chat transcripts (unverified report)

On November 9, 2026, Notion announced that a security incident at its vendor Fireworks AI may have exposed some Notion AI chat transcripts. According to piyolog's summary, the records are those used by the Insights feature, the impact is under 1% of all workspaces, and the investigation is ongoing.

4 min read

OBSERVED
CATEGORY
other
BLAST RADIUS
data
DETECTED BY
vendor-notification
TAGS
#notion #notion-ai #fireworks-ai #vendor-breach #supply-chain #zero-data-retention #insights #chat-transcripts #api-key-exposure

CH 1

Cause

In October 2026, Fireworks confirmed two intrusion routes: misuse of internal credentials, and access to a development machine through a third-party cloud provider. Fireworks had promised by contract not to retain Notion's data, but Notion's investigation found that data had been retained on the Fireworks endpoints it used.

CH 2

Consequence

The records that may have been exposed include chat inputs and outputs. Notion API keys were also found inside affected users' messages, and Notion revoked them on November 11. Six organizations in Japan disclosed impact; RECEPTIONIST cites information on 53 outside people, and One Career cites up to about 2,300 items of personal information.

CH 3

Fix

By the morning of November 3, 2026, Notion had cut its connection to Fireworks and deleted the data, and it stopped the Insights feature and the open-weight models served through Fireworks. It emailed owners of affected workspaces on November 9. It says it will check compliance with data minimization, including ZDR, when auditing critical vendors.

What happened

On November 9, 2026, Notion announced that a security incident at its vendor Fireworks AI may have exposed some Notion AI chat transcripts. What follows is based on a piyolog article that compiles the announcements from Notion and Fireworks.

Fireworks identified misuse of internal credentials on October 6, 2026, and on October 24 also detected an intrusion through a third-party cloud provider. Notice to Notion began on the night of November 2, when it concerned a small dataset containing synthetic test data. On November 6 Fireworks said a malicious party may have accessed information that appeared to be customer data, and on November 8 it provided the final affected dataset.

Per Notion's announcement, the impact is under 1% of all workspaces and the investigation is ongoing. Notion's announcement does not say which intrusion route or dates may have touched Notion's data.

The chaos on the ground

By the morning of November 3, Notion had cut its connection to Fireworks as a precaution and deleted all data held there. It also stopped sending data and traffic and halted all training jobs. On November 9 it emailed the owners of affected workspaces, and it disabled the Insights feature and stopped serving open-weight models through Fireworks.

When Notion analyzed the dataset it received on November 8, it found Notion AI chat transcripts used by the Insights feature. In most affected workspaces the records carry no speaker or workspace labels and contain no tool-call results. Apart from the wording inside the records, nothing links a workspace, user or company to them.

Companies in Japan also began disclosing impact one after another. piyolog could confirm six organizations; One Career was notified by Notion on November 11 and the other five on November 10. Their notices say that parts of the inputs and AI responses, including client contact names and inquiry contents, may be affected.

Root cause

There were two intrusion routes at Fireworks. The first was misuse of internal credentials: an unauthorized party accessed the environment variables used by evaluation jobs in some customer accounts. Fireworks believes environment variables holding API keys and tokens stored as secrets were taken.

The second was a breach of the third-party cloud provider that hosted Fireworks' research and development machines. A security incident occurred at that provider on October 23, and on October 24 an unauthorized party used that route to reach a Fireworks development machine. Fireworks' CEO explained that the party escalated privileges over several hops, assumed one of the cloud service accounts, and accessed part of the storage systems. Fireworks says there is evidence linking the activity to a financially motivated group targeting "LLMJacking".

On Notion's side, Insights was the way the data got out. Notion sent stored Notion AI requests and responses to Fireworks for classification, and Notion's Enterprise zero-data-retention promise excludes features that need such storage. Fireworks had promised by contract not to retain Notion's data, but Notion's investigation found data retained on the endpoints it used. Neither company has said which Fireworks feature stored it.

The fix

Notion recommends treating the affected data as leaked, and asks anyone who pasted credentials such as passwords or API keys into Notion AI during the incident period to change or reissue them. The investigation found Notion API keys inside affected users' messages, and Notion revoked them on November 11. Workspaces Notion has not contacted have not been identified as affected and need no action for now.

Owners of affected workspaces can review the affected data under "Security incident review" in the sidebar. Owners of workspaces with a verified domain can also get an annotated CSV. Notion says it will check compliance with data minimization, including ZDR, when auditing critical vendors such as inference providers and data processors.

On its side, Fireworks is replacing credentials and service accounts, removing unnecessary elevated privileges, isolating networks and strengthening logging and monitoring, with help from Palo Alto Networks Unit 42. The lesson for operators is to verify that a vendor actually honors a contractual promise not to retain data, rather than relying on the contract alone. Notion's investigation shows that the promise and the reality can differ.

Sources

PREFLIGHTIs your own Mac prepared?BB Preflight is a free Mac tool that checks 21 things, from AI agent permissions to where your keys live, without changing anything.Run the check →