Actively exploited Security news

Fireworks AI breach: Notion AI chat transcripts, billing data and, per TechCrunch, Uber drivers' licence details

Fireworks AI, a platform companies use to run open AI models, suffered two intrusions in October 2026. Notion has confirmed that Notion AI chat transcripts from fewer than 1% of workspaces were taken, and Uber is notifying drivers about a breach at a vendor. Fireworks links the attacks to a criminal group that resells access to language models (LLMJacking).

Kyberkit editorial team · · event date · reading time 4 minutes · For admins and analysts

Actively exploited: Fireworks AI breach hits Notion and Uber drivers

Key points

  • On 6 October 2026 Fireworks AI detected misuse of internal credentials: the attacker read environment variables from evaluation jobs, meaning some customers' API keys and tokens.
  • A second intrusion came through a security incident at a cloud provider hosting Fireworks R&D machines (23 Oct). Per the 9 November update, account and billing data was exposed and, for a limited set of accounts, secrets, datasets and incomplete model weights. Payment card numbers were not.
  • Notion confirmed that Notion AI chat transcripts (from the Insights feature and the voluntary LEAP programme) were exposed for fewer than 1% of workspaces. Notion says the data was retained at Fireworks despite a contractual zero-retention commitment.
  • Uber has filed breach notices citing a 7 October 2026 incident at a third-party vendor. TechCrunch reports the vendor is Fireworks AI and that drivers' licence details were taken; Uber has not named the vendor.

What happened

Fireworks AI is a platform developers and companies use to run open AI models. Its own bulletins describe two intrusions. In the first, on 6 October 2026, an attacker misused internal credentials and reached environment variables in evaluation jobs - the API keys and tokens some customers had stored there. Fireworks revoked the keys and began emailing affected customers on 7 October.

The second came through a cloud provider that hosted Fireworks R&D machines and had its own security incident on 23 October. On 24 October the attacker used that foothold to reach Fireworks development machines and run an unauthorised workload. In a 9 November update Fireworks widened the scope: account and billing information (addresses, invoice and payment history, balance, credit usage) was exposed and, for a limited set of accounts, secrets, datasets and incomplete model weights. Fireworks does not store card numbers. It says Inference, the Training SDK and Nexus were not affected.

Fireworks links the activity to a financially motivated criminal group that resells language model access through illicit gateways - LLMJacking, which we covered in our report on Google GTIG's findings.

Who is affected

  • Notion used Fireworks for its Insights feature (which shows admins how a workspace uses AI) and for open-weight models. The breach affects fewer than 1% of workspaces and covers the full text of Notion AI chats and model output - including names, email addresses or tokens if someone typed them in. Notion found the data had been retained at Fireworks despite a contractual zero-retention commitment. On 3 November it cut the connection and switched off Insights.
  • Uber cites a 7 October 2026 breach date in its notice to the California Attorney General. According to TechCrunch, Uber is telling drivers about an incident at a third-party vendor, which TechCrunch identifies as Fireworks AI, and personal and driver's licence information was taken. TechCrunch counted more than 7,800 people across filings in three US states. Uber has not publicly named the vendor and refers questions to Fireworks.
  • Other Fireworks customers: the company has not published numbers and is contacting those affected by email.

What to do

  1. Fireworks customers with a notice: create new API keys, rotate the third-party credentials listed in the notice with their issuers and review what they could reach. Look for unfamiliar keys, users, evaluators and training jobs.
  2. Affected Notion users: download the data summary from the sidebar (? → Security incident review) and immediately rotate any password, key or token you ever pasted into a chat.
  3. Uber drivers with a notice: expect phishing and scam calls using Uber's name. Check suspicious links with our Link Checker.
  4. Organisations in general: verify that AI vendors really do not retain your data, and keep secrets out of AI chats - they belong in a secrets manager. Barracuda has just described a similar vendor-driven chain.

Timeline

  • 6 Oct 2026 - Fireworks detects misuse of internal credentials.
  • 7 Oct 2026 - breach date in Uber's notice.
  • 9 Oct 2026 - first Fireworks bulletin.
  • 23-24 Oct 2026 - cloud provider incident and second intrusion.
  • 3-4 Nov 2026 - Notion disconnects Fireworks; data deleted.
  • 9 Nov 2026 - Fireworks widens the scope of the breach.
  • 13 Nov 2026 - reports of Uber's notices to drivers.

Details on Fireworks and Notion come from their own pages (checked 16 November 2026). The link between Uber's breach and Fireworks, and the driver counts, are as reported by TechCrunch; Uber does not name the vendor and we have not seen its notice.

Updates

  • 16 Nov 2026 (evening) - according to an updated TechCrunch report, Uber's notice to the Oregon attorney general lists 149,346 affected people in total; Uber did not say how many of them are drivers, TechCrunch reports. We have not seen the notice itself, so the figure is TechCrunch's claim. Uber also filed a notice in Iowa (10 Nov).
  • 16 Nov 2026 - Cursor is another victim: according to its 13 Nov update, the attacker obtained an access key Cursor had issued to Fireworks and, using data from Cursor's bucket, eventually pushed a tampered Claude Code extension into Cursor's marketplace (29 Oct, up to 5,000 users). Details and indicators in Cursor: tampered Claude Code extension via Fireworks key.

FAQ

I use Notion. Am I affected?

Notion says fewer than 1% of workspaces are. If neither you nor your workspace owner has heard from Notion, your workspace has not been identified as affected and no action is needed.

What exactly leaked from Notion AI?

The full text of Notion AI chat messages and the model's replies, possibly including text selected on the page. If you ever pasted a password, key or token into a chat, it may have leaked. Notion says attachments and most tool use were not affected.

Were Fireworks customers' card numbers exposed?

No. Fireworks says it does not store card numbers. Billing and shipping addresses, invoice and payment history, account balance and credit usage were exposed.

What is LLMJacking?

Theft of access to language models: attackers steal AI service keys and resell the capacity through illicit gateways, leaving the victim to pay the usage bill.

Sources

  1. Fireworks AI - October 2026 security incident (9 Oct 2026, updated 10 Oct)
  2. Fireworks AI - October 2026 security incident update (updated 9 Nov 2026)
  3. Notion - Security incident involving a third-party AI vendor
  4. California Attorney General - data breach notice: Uber Technologies, Inc. (breach date 7 Oct 2026)
  5. TechCrunch - Uber confirms hackers stole thousands of drivers' license information in data breach (13 Nov 2026)

Spotted a mistake? Let us know and we will correct it openly.