--- title: "Fireworks AI October security incidents" description: "Fireworks disclosed October credential misuse and development-machine compromise; Notion later confirmed impact to AI chat transcripts." incident_type: "Cybersecurity incident" status: "active" last_modified: "2026-11-10" canonical_url: "https://www.ally.security/incidents/fireworks-ai-october-security-incidents-2026" markdown_url: "https://www.ally.security/incidents/fireworks-ai-october-security-incidents-2026.md" stix_url: "https://www.ally.security/incidents/fireworks-ai-october-security-incidents-2026/stix.json" --- # Fireworks AI October security incidents October activity exposed secrets and other customer data, with downstream impact to Notion AI Insights. Last modified Nov 10, 2026 · 3 sources ## Summary - **Environment:** Evaluation secrets, development machines and stored datasets - **Operational impact:** Dataset transfers and Notion Insights disabled during investigation - **Financial impact:** No confirmed incident cost quantified ## What happened [Fireworks AI](https://fireworks.ai/) detected misuse of internal credentials on October 6, exposing evaluation-job secrets in a limited set of customer accounts. Its [initial bulletin](https://fireworks.ai/security/bulletins/october-2026-security-incident) was published October 9. [3](#source-3) A [November 9 update](https://fireworks.ai/security/bulletins/october-2026-security-incident-update) described further activity: attackers reached development machines through an unnamed cloud provider on October 24 and ran an unauthorized workload. [2](#source-2) ## Impact - Fireworks broadened its findings to resource metadata, billing information, and—for some accounts—secrets, datasets and incomplete model weights. Card numbers were excluded. The update does not assign every category to a particular intrusion. [2](#source-2) - [Notion](https://www.notion.com/) reported affected Insights chat transcripts in fewer than 1% of workspaces. Most lacked user/workspace labels and tool-call results; the text itself could still contain identifying or sensitive information. [1](#source-1) ## Timeline ### October 6, 2026 — Credential misuse detected Containment began the same day. [3](#source-3) ### October 7, 2026 — Customer notification begins Affected customers began receiving notices. [3](#source-3) ### October 24, 2026 — Development-machine activity detected Fireworks detected the unauthorized workload following the provider’s October 23 compromise. [2](#source-2) ### November 3, 2026 — Notion disconnects Fireworks The initial November 2 warning concerned synthetic testing data. [1](#source-1) ### November 8, 2026 — Additional dataset confirmed Following a November 6 warning, Notion identified customer-chat impact in the confirmed dataset. [1](#source-1) ### November 10, 2026 — Briefing updated This briefing was last reviewed and updated on November 10, 2026. ## Threat Group & Attack Vector The first activity involved internal credentials; the later entry used a compromised hosting provider. Fireworks has not identified that provider or a specific exploited vulnerability. [2](#source-2) [3](#source-3) ### Actors - No threat actor group has been identified in the reviewed public evidence. ### TTPs - [T1078 — Valid Accounts](https://attack.mitre.org/techniques/T1078/): internal credentials were used without authorization. [3](#source-3) ## Response Fireworks revoked keys and requested rotation of exposed third-party credentials. [3](#source-3) It engaged [Unit 42](https://unit42.paloaltonetworks.com/), restricted systems and disabled self-service dataset transfers. Its investigation remained open. [2](#source-2) Notion’s [advisory](https://www.notion.com/en-gb/security/advisories/security-incident-involving-a-third-party-ai-vendor) says Insights was disabled, Fireworks-based open-weight inference stopped, and affected customers contacted with access to their impacted data. [1](#source-1) ## Assets [Download the case-scoped STIX 2.1 bundle]() ## Sources Primary source records used to research this incident. ### Fireworks AI incident official · Notion · Nov 9, 2026 ### Update on October 2026 security incident official · Fireworks AI · Nov 9, 2026 ### Fireworks October 2026 security incident official · Fireworks AI · Oct 9, 2026
Evidence ledger Review the supporting structured claims. 1. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Fireworks confirms additional dataset to Notion 2. **Affected Organization · 100% confidence · current** Fireworks AI October security incidents: Fireworks AI 3. **Used Attack Technique · 100% confidence · current** Fireworks AI October security incidents: https://attack.mitre.org/techniques/T1078/ 4. **Occurred At · 100% confidence · current** Fireworks development-machine compromise on October 24: 2026-10-24 5. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Fireworks publishes initial bulletin 6. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Fireworks revoked identified internal credentials, affected API keys and attacker-created keys, and told affected customers to rotate third-party credentials with their issuers. 7. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Fireworks involved law enforcement and Unit 42, rotated credentials, isolated systems and disabled self-service dataset uploads and downloads for Batch Inference and dataset-based training during investigation. 8. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Fireworks begins affected-customer notifications 9. **Affected Organization · 100% confidence · current** Fireworks AI October security incidents: Notion 10. **Occurred At · 100% confidence · current** Notion disconnects Fireworks after initial synthetic-data notice: 2026-11-03 11. **Resulted In · 100% confidence · current** Fireworks development-machine compromise on October 24: Fireworks detects development-machine activity 12. **Processor For · 100% confidence · current** Fireworks AI: Notion 13. **Occurred At · 100% confidence · current** Fireworks publishes initial bulletin: 2026-10-09 14. **Resulted In · 100% confidence · current** Fireworks development-machine compromise on October 24: After an unnamed hosting provider was compromised on October 23, the attacker reached Fireworks development machines on October 24 and ran an unauthorized workload, causing additional customer-data impact. 15. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Notion initially identified synthetic testing data after November 2 notification and disconnected Fireworks by November 3. A November 6 warning and November 8 dataset confirmation then revealed customer-chat impact. 16. **Discovered At · 100% confidence · current** Fireworks development-machine compromise on October 24: 2026-10-24 17. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Fireworks said payment-card numbers were not stored and were unaffected; it had not detected impact to Inference, Training SDK or Nexus. 18. **Affected Organization · 100% confidence · current** Fireworks development-machine compromise on October 24: Fireworks AI 19. **Occurred At · 100% confidence · current** Fireworks confirms additional dataset to Notion: 2026-11-08 20. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Notion disabled Insights, stopped using Fireworks for open-weight models, contacted affected customers and offered access to impacted data inside their workspaces. 21. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: The October 10 assessment found no evidence of access to models, datasets, training data, personal information or inference traffic; this was an interim assessment later broadened by the November update. 22. **Occurred At · 100% confidence · current** Fireworks detects development-machine activity: 2026-10-24 23. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: By November 9, Fireworks reported affected resource metadata and billing details, plus secrets, datasets and incomplete model weights for a limited set of accounts. The update does not allocate every data category to a specific intrusion. 24. **Resulted In · 100% confidence · current** Fireworks development-machine compromise on October 24: Fireworks reported no further detected successful attacker access to its customer platform as of October 25; the investigation remained open. 25. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Notion disconnects Fireworks after initial synthetic-data notice 26. **Disclosed At · 100% confidence · current** Fireworks AI October security incidents: 2026-10-09 27. **Occurred At · 100% confidence · current** Fireworks begins affected-customer notifications: 2026-10-07 28. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Fireworks identified misuse of internal credentials and access to secrets used by evaluation jobs in a limited set of customer accounts. 29. **Occurred At · 100% confidence · current** Fireworks detects credential misuse and begins containment: 2026-10-06 30. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Fireworks detects credential misuse and begins containment 31. **Discovered At · 100% confidence · current** Fireworks AI October security incidents: 2026-10-06 32. **Resulted In · 100% confidence · current** Fireworks AI October security incidents: Notion reported impact to fewer than 1% of workspaces, involving Notion AI chat transcripts used by Insights. For the vast majority of affected workspaces, transcripts lacked user and workspace labels and tool-call results; transcript text itself could still identify information.