Skip to main content
a promotional graphic telling you that PCI Compliance is no longer an annual exercise and that continuous monitory must be built in
IncidentSeverity S: serious, 4/5Confirmed: a company, official or court statement

Fireworks AI disclosed a second breach in weeks, with a hacked cloud provider exposing customer data

Fireworks AI, a startup that helps companies run AI models, notified customers that an unauthorized third party breached an external cloud provider hosting its research and development machines. Fireworks said the incident happened on Oct. 24. A person familiar with the matter said tens of thousands of files were involved, some containing customer data. According to the company, the exposed data included billing and shipping addresses, invoices, payment histories and, for some customers, datasets and parts of incomplete AI model weights. Notion confirmed that some of its AI chat transcripts were exposed and that fewer than 1% of its workspaces may have been affected. Fireworks also confirmed that a separate early October breach, involving unauthorized use of internal Fireworks credentials, affected customers' account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models. Fireworks said it is working with customers including Notion and Cursor, has engaged Palo Alto Networks and has notified law enforcement.

What the AI did

No AI system acted on its own. Attackers broke into infrastructure that Fireworks AI uses to run and develop AI models. They reached customer datasets, incomplete AI model weights and, through Notion, the content of AI chat conversations.

First reported November 10, 2026 · Added to the register November 16, 2026 · 3 sources

Deployer
Fireworks AI
Affected
Notion, Cursor and others, Notion, Render
When it happened
October 24, 2026
First reported
November 10, 2026

What this means for you

Could this affect you?

Yes

If you use Fireworks AI to host or run AI models. Companies that use Fireworks AI, including Notion and Cursor, may have had account, billing and dataset information exposed. In some cases secrets and models stored on the platform were also exposed. Notion AI conversations from a small share of Notion workspaces were exposed too.

What to check

  • Rotate any credentials and API secrets (access keys for software) stored on Fireworks AI.
  • Review what data and models you uploaded to Fireworks AI.
  • Assess the security of an AI provider's underlying cloud hosting during vendor due diligence.

Timeline

  1. October 24, 2026Happened
  2. November 10, 2026First reported
  3. November 11, 2026Notion confirmed that some of its AI chat transcripts were exposed in the Fireworks AI breach and that fewer than 1% of its workspaces may have been affected; Render's CEO shared a notification from Notion on X confirming that Render was among the affected customers.[2]
  4. November 12, 2026Notion said that on November 3 it disconnected its systems from Fireworks, deleted the data stored in its systems and stopped all connectivity between the two, and confirmed the stolen chat transcripts came from Notion AI customers who used the “Insights” feature. Fireworks said it believes the hackers are financially motivated, with goals focused on selling tokens from breaching access to large language models.[3]
Every fact and its source (14)
  1. Date of latest breachOct. 24
    “This incident happened on Oct. 24, Fireworks said.”[1]
  2. Notion disconnected from FireworksNovember 3
    “On November 3, Notion said it disconnected its systems from Fireworks”[3]
  3. ResponseInvestigation with Palo Alto Networks; law enforcement notified
    “Fireworks launched an investigation with support from the cybersecurity firm Palo Alto Networks Inc. and notified law enforcement”[1]
  4. Attribution of October breachCybercriminal threat actor group
    “evidence links a cybercriminal threat actor group to the early October incident”[1]
  5. Data affected in October breachSecrets, datasets and incomplete models for a limited set of accounts
    “secrets, datasets and incomplete models”[1]
  6. Earlier October breachUnauthorized use of internal credentials to access customer accounts
    “unauthorized use of internal Fireworks credentials to get access to a number of customer accounts”[1]
  7. Scale of files involvedTens of thousands of files, some with customer data
    “The breach included tens of thousands of files that contained customer data in some cases”[1]
  8. Breach vectorExternal cloud provider hosting Fireworks' machines was breached
    “an unauthorized third-party breached an external cloud provider that hosts the company’s machines”[1]
  9. Share of Notion workspaces possibly affectedfewer than 1%
    “Notion confirmed that fewer than 1% of its workspaces may have been affected.”[2]
  10. Suspected attackerFinancially motivated group interested in LLM-jacking
    “points to a financially motivated cybercriminal group interested in LLM-jacking”[2]
  11. Data exposed in second breachResource metadata, billing and shipping addresses, invoices, payment histories, account balances and credit usage
    “Attackers accessed resource metadata, billing and shipping addresses, invoices, payment histories, account balances, and credit usage.”[2]
  12. AI assets exposed in second breachSubsets of incomplete AI model weights and datasets for some customers
    “Some customers also had subsets of incomplete AI model weights and datasets exposed.”[2]
  13. Data taken from NotionChat transcripts of Notion AI Insights users
    “the hackers took chat transcripts of its Notion AI customers who used the “Insights” feature”[3]
  14. Suspected attacker motiveSelling access to LLMs
    “their goals are focused on selling tokens from breaching access to large language models”[3]

Sources

  1. Nvidia-Backed Fireworks AI Notifies Customers of Its Second Hack in Weeks
    insurancejournal.com · November 10, 2026
  2. Fireworks AI Breach Exposes Notion AI Chat Transcripts
    esecurityplanet.com · November 11, 2026
  3. Cyberattack on Fireworks AI allowed hackers to access Notion customers' chat transcripts
    techcrunch.com · November 12, 2026

How this record is classified. Severity S (4/5): real harm to one organisation, data exposed, or a containment failure. OECD level: incident, an event in which an AI system led to actual harm. Evidence: Confirmed, meaning a company, official or court statement.

The facts in At a glance and in Every fact and its source are quoted from the sources listed. The summary, What the AI did and What this means for you are written from those sources and checked against them automatically before publication. Records reflect what has been disclosed, not everything that has happened. Incidents are found through news feeds and the GDELT Project.

Promotional banner for the CUI buildout guide