Skip to main content
Back
Early noticeIntrusionSaaS

Fireworks AI October 2026 security incident

Fireworks AI reports unauthorized use of its internal credentials, impact to secrets and data in a limited set of customer accounts, and access to its development machines after a security incident at a third-party cloud provider that it does not name, and Cursor reports that a key it had issued to Fireworks was used to copy its shared storage bucket, but no source says how the credentials were obtained, how the machines were reached or which cloud is involved.

Technical account not yet published

This page holds what the public reporting states so far. We check for new reporting every day, and a full breakdown with the replay and the controls replaces this notice once a technical account is published.

Victim
Fireworks AI and customers of its platform
When
Not stated; identified October 6, 2026Disclosed Oct 9, 2026
Notice
Published Nov 10, 2026Updated Nov 16, 2026

What is known so far

  • On October 6, 2026 Fireworks AI identified unauthorized use of internal Fireworks credentials and began containment. Fireworks says an unauthorized third party accessed environment variables used in evaluation jobs in a limited number of customer accounts, and believes that environment variables, among them API keys and tokens stored as secrets, were captured in certain affected accounts. It began to notify affected customers on October 7. It says it revoked the internal credentials used in the incident, the affected Fireworks API keys and the keys it identified as created by the actor, and it told customers to rotate the third-party credentials listed in their notice with the providers that issued them. [1]
  • Uber says a service provider told it on October 9 that an unauthorized third party had compromised the provider's internal credentials and used them to access Uber's account with the provider. Uber says it then severed its data connections with the provider, and on October 13 found that the credentials had been used to access Uber data connected to the provider, among it personal information. Uber's filing with the California Attorney General gives October 7, 2026 as the date of the breach. Uber says it had not identified misuse of the data as of its notice. The notice does not name the provider; TechCrunch reports that an Uber spokesperson named Fireworks. [4, 5, 6]
  • Fireworks says a third-party cloud provider that hosted Fireworks R&D machines had a security incident on October 23, and that on October 24 the unauthorized third party used it to reach Fireworks development machines and then ran an unauthorized workload, which led to additional customer data impact. Fireworks does not name the provider. It says it detected the activity the same day and took remediation measures, among them to close known critical vulnerabilities that it does not name, and that as of October 25 it had not detected further evidence of successful unauthorized access to the platform its customers use. According to a post by the Fireworks CEO on X, as the Resilient Cyber newsletter paraphrases it, the attacker escalated through multiple hops to assume a cloud service account and reached a subset of storage systems. The newsletter names no cloud, account or storage service. [2, 12]
  • Cursor, a Fireworks customer, says an attacker obtained an access key that Cursor had issued to Fireworks, which Cursor says Fireworks exposed, and used it to copy data from a read-only storage bucket that Cursor used to share data with Fireworks. Cursor names neither the storage service nor its cloud, and gives no date for the copy. It says the bucket held limited coding-agent traces, mostly from 2025, some with credentials that had not been redacted, and that with those credentials the attacker reached select SaaS tools that Cursor uses and read archived non-production repositories, limited support data and other internal data. [8]
  • Cursor says that on October 29 the attacker used a stolen credential taken from that internal data to place malicious copies of the Claude Code extension on the cache that serves the Cursor extension marketplace, where at most 5,000 users could have received them. Cursor's notice puts the malicious build in the marketplace from about 09:27 to 20:35 UTC that day. Cursor says the last attacker activity it has seen, on November 1, was blocked, and that it moved inference off Fireworks, deactivated the key it had issued to Fireworks and cut Fireworks' access to shared datasets. [8, 9]
  • In its update of November 9 Fireworks says it has since found impact to account and billing information and, for a limited set of accounts, to secrets, datasets and incomplete models. It says the affected internal application gave access to resource metadata, to billing information and, for certain customers, to a subset of incomplete model weights and datasets. It says it does not store payment card numbers and that they were not impacted, and it reports no impact to Inference, the Training SDK or Nexus. The Register reports that the Fireworks CEO wrote on X: "From what we see attackers are not after weights." It also reports the remark by the CEO that most downloads were partial and stopped. [2, 10]
  • On attribution Fireworks writes: "The evidence indicates links to a cybercriminal threat actor group". It describes the group as financially motivated and says the group sells tokens, gained by unauthorized access to large language models, to illicit routing gateways, which it calls LLMjacking. It does not name the group. Bloomberg, in a copy syndicated by Claims Journal, reports that the evidence ties the group to the activity of early October and that Fireworks did not say who was responsible for the activity of October 24. Fireworks says it notified law enforcement and obtained forensic help from Palo Alto Networks Unit 42, with which it revoked and replaced credentials and service accounts and removed unnecessary elevated privileges. It disabled self-serve dataset uploads and downloads while the investigation runs, and says its findings rest on the investigation to date, which continues. [2, 11]
  • Notion, a Fireworks customer, says Fireworks told it on November 2 that malicious actors had accessed a small set of data that held Notion AI synthetic testing data and no customer data. Notion says it disconnected its systems from Fireworks on November 3 and deleted all of its data in the Fireworks system on November 4. [7, 3]
  • Notion says Fireworks told it on November 6 that malicious actors may have accessed potential customer data, and confirmed the final impacted dataset on November 8: Notion AI chat transcripts used for its Insights feature, for most affected workspaces not attributable to a user, company or workspace. Notion says fewer than 1% of its workspaces are affected. It says Fireworks had committed by contract to zero data retention, but that data from the endpoints Notion used was retained. Notion revoked exposed Notion API keys found in affected messages on November 11 and reported exposed third-party API keys to their issuers on November 12. [7, 3]
  • Uber's notice counts approximately 1,873 affected Rhode Island residents as of November 10, 2026. TechCrunch reports that state filings, as of November 13, 2026, count 2,567 people in Massachusetts, whose filing names driver's license information, and 3,430 people in South Carolina, and that Illinois and California gave no count. No source gives a total. TechCrunch reports that a Fireworks spokesperson confirmed unauthorized access to some of its systems that affected customer data. [4, 6]

What is not published yet

  • How the internal Fireworks credentials were obtained.
  • Which class of credential they were, and which system accepted them.
  • How the environment variables of evaluation jobs were read.
  • When the unauthorized activity began.
  • Which credential reached Uber's account with Fireworks, what that account holds and where Uber's data was stored.
  • Whether the access to Uber data belongs to the activity of early October.
  • The name of the third-party cloud provider that had the security incident of October 23.
  • How that incident gave access to the Fireworks development machines.
  • What the unauthorized workload was and where it ran.
  • Which cloud service account was assumed, through which hops, and which storage systems it reached.
  • Whether the actor of October 24 is the actor of early October.
  • Which Fireworks activity exposed the key that Cursor had issued to Fireworks, and which class of key it was.
  • Which internal application was affected, and how it was reached.
  • Which cloud providers host the Fireworks systems involved, and which storage service and cloud held the bucket that Cursor shared with Fireworks.
  • The number of affected customer accounts, and the total number of people whose data was accessed.
  • Whether other exposed customer secrets were used at the providers that issued them.
  • The name of the threat actor group.

Sources

Every fact in this notice comes from the public reporting below. A full breakdown, with the replay and the controls, replaces the notice when a technical account is published.

  1. 1.
    Fireworks October 2026 security incidentFireworks AI · Oct 10, 2026 · Vendor reportthe first activity, the scope as of October 10, the first response, the customer guidance
  2. 2.
    Update on October 2026 security incidentFireworks AI · Nov 9, 2026 · Vendor reportthe further activity of October 23 and 24, the data involved, the attribution as hedged, the forensic firm, the remediation
  3. 3.
    Notice about the Fireworks AI incident that may impact some Notion workspacesNotion · undated · Vendor reportone affected customer's own statement, the data it held at Fireworks, the retention of that data, its disconnection and deletion
  4. 4.
    Notice of Security Incident (multistate template)Uber Technologies, Inc. (filed with the California Attorney General) · Nov 10, 2026 · Vendor reportone affected customer's own notice, what the compromised internal credentials reached at the customer, the notification and confirmation dates, the Rhode Island count, the customer's response
  5. 5.
    Submitted Breach Notification Sample: Uber Technologies, Inc.California Attorney General · Nov 10, 2026 · Advisorythe date of the breach as Uber filed it, the filing date
  6. 6.
    Uber confirms hackers stole thousands of drivers' license information in data breachTechCrunch · Nov 13, 2026 · Newsthe vendor named by Uber's spokesperson, the per-state counts, the data type, the Fireworks response
  7. 7.
    Security incident involving a third-party AI vendorNotion · Nov 13, 2026 · Vendor reportone affected customer's timeline from November 2 to 12, the datasets involved, the share of workspaces, the key revocation
  8. 8.
    An update on our recent security incidentCursor · Nov 13, 2026 · Vendor reportone affected customer's own account: the use of a key it had issued to Fireworks, the copy of its shared bucket, the later access at the customer, its response
  9. 9.
  10. 10.
    Fireworks AI gets burned twice as customer data exposure widensThe Register · Nov 10, 2026 · Newsthe CEO's remarks on model weights and downloads, as reported
  11. 11.
    Nvidia-Backed Fireworks AI Notifies Customers of Its Second Hack in WeeksClaims Journal (syndicating Bloomberg) · Nov 10, 2026 · Newsthe scope of the attribution, as reported
  12. 12.
    The Resilient Brief: Five OpenAI Eval Agents Got Root and Vulns Prove DenseResilient Cyber · Nov 12, 2026 · Newsthe CEO's account of escalation to a cloud service account and storage systems, as paraphrased

This notice is written from public reporting while the incident is still being disclosed. It names no control and gives no verdict, because the sources do not yet say what was used against what. It is not an assessment of the victim's security program.