Skip to content
The Cybersecurity Focus
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
AIBreachIncident

Notion AI Chat Transcripts Exposed in Fireworks AI Third-Party Data Breach

By ogwatermelon
November 13, 2026 4 Min Read
0
November 12, 2026

Notion disclosed that a security breach at its AI infrastructure provider, Fireworks AI, exposed Notion AI chat transcripts in a small number of workspaces. The incident highlights growing third-party supply chain risks in the generative AI ecosystem, where customer data passes through multiple vendors for model inference and analytics.

What Happened: Fireworks AI Breach Exposes Notion AI Chat Transcripts

On November 11, 2026, Notion published a security advisory confirming that customer AI chat transcripts were accessed during a breach at Fireworks AI. Fireworks AI is the third-party provider that enables Notion to run open-weight models and power the Insights analytics feature for Notion AI.

The breach itself began on October 23, 2026, when an attacker accessed Fireworks AI’s development environment through a compromised third-party cloud provider. Consequently, the attacker was able to view resource metadata, billing information, model weights, and datasets for some Fireworks customers. Fireworks AI had also experienced a separate breach in early October, when attackers accessed environment variables containing API keys and tokens.

Notion first learned of the issue on November 2 through an alert from Fireworks about an exposed dataset. Initially, Fireworks indicated the dataset contained only synthetic test data. However, Fireworks confirmed on November 8 that actual customer data had been accessed, including Notion AI transcripts.

Technical Details of the Third-Party Data Exposure

The exposed data came from the Insights dataset, a feature that gives workspace administrators visibility into how teams use Notion AI. Fireworks AI processes and stores these transcripts to generate analytics for the Insights feature.

Key technical aspects of the incident include:

  • Breach vector: Third-party cloud provider compromise at Fireworks AI
  • Initial intrusion date: October 23, 2026
  • Data type exposed: Notion AI chat transcripts from the Insights dataset
  • Attribution: For most impacted workspaces, the chats were unattributable
  • Scope: Less than 1% of Notion users affected

What “Unattributable” Means for Impacted Users

Notion emphasized that for the vast majority of impacted workspaces, the exposed transcripts were unattributable. This means the chats were not labeled with the author or originating workspace. Furthermore, the transcripts did not contain tool call results. However, users who entered credentials, API keys, or other sensitive information directly into AI chat sessions should rotate those secrets immediately.

Business and Operational Impact

Third-party AI supply chain breaches are becoming a recurring risk as organizations integrate generative AI services into their workflows. This incident carries several implications for businesses relying on AI-powered platforms:

  • Data exposure: AI chat transcripts may contain sensitive business discussions, proprietary strategies, or inadvertently shared credentials.
  • Trust erosion: Customers expect zero data retention from AI vendors, yet contractual commitments did not prevent exposure in this case.
  • Compliance implications: Organizations in regulated industries may face questions about how third-party AI vendors handle and store conversation data.
  • Operational disruption: Notion disabled the Insights feature and severed its Fireworks AI integration, removing analytics capabilities for administrators.
  • Supply chain cascade: A breach at one AI infrastructure provider can ripple downstream to every SaaS platform that relies on it.

Mitigation and Recommendations

Immediate Actions for Defenders

  1. Audit AI vendor contracts. Review data retention, processing, and breach notification clauses in agreements with AI infrastructure providers.
  2. Rotate exposed credentials. If passwords, API keys, or tokens were entered into affected AI chat sessions, rotate them immediately.
  3. Review AI usage policies. Establish clear guidance on what employees may share with AI assistants, especially in multi-tenant SaaS environments.
  4. Disable unnecessary AI features. Features like conversation analytics increase data exposure surface area. Disable them if not required.
  5. Assess third-party risk. Map all AI vendors in your supply chain and evaluate their security practices, breach history, and data handling procedures.

Long-Term Supply Chain Security

  • Require AI vendors to provide evidence of zero data retention and encryption at rest.
  • Implement data loss prevention (DLP) policies that monitor and restrict sensitive data entry into AI chat interfaces.
  • Evaluate whether on-premises or self-hosted AI models reduce third-party exposure for high-risk use cases.
  • Monitor for future advisories from AI infrastructure providers and SaaS platforms you rely on.

Bottom line: The Notion and Fireworks AI incident is a reminder that generative AI supply chains introduce new data exposure risks. Organizations must scrutinize how their AI vendors handle conversation data and establish guardrails for what employees share with AI assistants.

Incident Summary

Incident: Fireworks AI breach exposing Notion AI chat transcripts
Affected Systems: Notion AI Insights feature (powered by Fireworks AI)
Disclosure Date: November 11, 2026
Initial Intrusion Date: October 23, 2026
Patch Status: N/A — third-party incident; Notion severed Fireworks integration and disabled Insights
Scope: Less than 1% of Notion users; transcripts largely unattributable

References

  1. Notion, “Security Incident Involving a Third-Party AI Vendor,” November 9, 2026, https://www.notion.com/security/advisories/security-incident-involving-a-third-party-ai-vendor-nov9, accessed November 12, 2026.
  2. Notion Help Center, “Security Incident Involving a Third-Party AI Vendor FAQ,” November 2026, https://www.notion.com/help/security-incident-invollying-a-third-party-ai-vendor, accessed November 12, 2026.
  3. BleepingComputer, “Notion says Fireworks breach exposed customer AI chat transcripts,” November 11, 2026, https://www.bleepingcomputer.com/news/security/notion-says-fireworks-breach-exposed-customer-ai-chat-transcripts/, accessed November 12, 2026.
  4. BleepingComputer, “Fireworks AI discloses new breach after cloud provider hack,” November 2026, https://www.bleepingcomputer.com/news/security/fireworks-ai-discloses-new-breach-after-cloud-provider-hack/, accessed November 12, 2026.

Tags:

AIBreachIncident
Author

ogwatermelon

Follow Me
Other Articles
Previous

Critical Apache HTTP/2 CVE Enables Unauthenticated Remote Code Execution

Next

Windows SignDrop Zero-Day Grants SYSTEM Privileges and Bypasses Any Antivirus

AI Android Backdoor Botnet Breach CVE Exploit Hack Incident Infostealer KEV Linux Mac Malware Network News Phishing Ransomware RCE supp supply chain Virtualization Vishing Vulnerability Windows World Worm Zero Day

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026

Categories

  • AI
  • Android
  • Apple
  • Backdoor
  • BotNet
  • Breach
  • CVE
  • exploit
  • Hack
  • Incident
  • Infostealer
  • KEV
  • Linux
  • Mac
  • Malware
  • News
  • Phishing
  • Ransomware
  • RCE
  • supply-chain
  • Uncategorized
  • Virtualization
  • Vishing
  • Vulnerability
  • Windows
  • World
  • Worm
  • Zero Day
Copyright 2026 — The Cybersecurity Focus. All rights reserved.