Skip to content
← Blog · · df00tech

Notion AI Chat Transcripts Exposed via Breach at Third-Party Provider Fireworks AI

security-news breach

What Happened

Notion disclosed that a security breach at Fireworks AI, a third-party AI infrastructure provider it uses, resulted in the exposure of Notion AI chat transcripts belonging to a small number of customer workspaces. Details on the scope, root cause, and timeline of the Fireworks AI breach itself have not been fully disclosed in current reporting.

Why It Matters

This incident is another reminder that AI feature integrations extend an organization's trust boundary to third-party model and infrastructure providers. Chat transcripts with an AI assistant embedded in a workspace tool like Notion can contain sensitive business context, internal data, credentials pasted for troubleshooting, or proprietary information that users may not expect to be exposed through a downstream vendor's infrastructure. Even when the number of affected workspaces is small, the exposure of conversational AI data raises concerns about what metadata, prompts, or content might be retained or logged by AI vendors supporting SaaS products.

What Defenders Should Do

  • Inventory which SaaS products in your environment embed third-party AI providers (model hosting, inference, or fine-tuning vendors) and understand their data retention and breach notification practices.
  • Review internal guidance on what employees should avoid pasting into AI chat features (secrets, credentials, customer PII, internal source code).
  • If you use Notion AI, watch for official notification from Notion regarding whether your workspace was affected, and review any AI chat history for sensitive content that may need rotation (e.g., exposed credentials or tokens).
  • Treat AI assistant transcripts as a data category in your DLP and data-classification programs, not just as ephemeral UI interactions.
  • Ask SaaS vendors directly about their subprocessor relationships for AI features and whether those subprocessors are covered under the vendor's own incident response and breach notification obligations.

Developing Story

This is based on a single report and details are still emerging, including the full scope of the Fireworks AI breach and how it led to transcript exposure. We will monitor for updates as Notion and Fireworks AI provide further information. Read the original reporting at BleepingComputer.

Get new detections in your inbox

New ATT&CK coverage plus CISA KEV / CVE detection rules, roughly weekly. No spam, unsubscribe anytime.