Skip to content

Intelligence briefFall/Winter 2026/2027 Edition

The Fireworks AI breach makes AI vendors a third-party risk tier

Stolen Fireworks AI credentials and an exposed access key reached customer data at Uber, Notion and Cursor. Inventory AI vendors and keys, minimize what you send, and rotate secrets when a vendor reports a breach.

At a glance

BA-03 · Breach analysis

  • 149,346 Uber drivers notified, per reported state filing[5]
  • 5,000 Most Cursor users who received the tampered extension[2]
  • <1% Notion workspaces affected[3]
  • 2 Separate Fireworks incidents in October[1]
Status
Ongoing risk. Fireworks' November 17 bulletin calls both October incidents contained and remediated, while Notion says its own investigation is continuing.[1]
Vendor
Fireworks AI, an inference and model hosting provider[1]
Fireworks incidents
Two separate incidents in October 2026[1]
Uber
Driver data; 149,346 people notified per state filing reporting[4]
Cursor
Exposed access key; at most 5,000 users received a tampered extension[2]
Notion
Fewer than 1% of workspaces; some AI chat transcripts[3]
Fireworks attribution
A financially motivated group tied to selling LLM tokens[1]

What happened

Fireworks AI disclosed two separate security incidents in October 2026. Customers Cursor, Notion and Uber each reported consequences tied to the Fireworks compromise. [1][2][3][4]

  • Fireworks says it identified unauthorized use of internal credentials on October 6. The attacker reached environment variables in evaluation jobs for a limited number of customer accounts, including API keys and tokens stored as secrets. [1]
  • A second incident ran from October 23 to October 30. Fireworks says an attacker reached development machines hosted by a third-party cloud provider, then part of production, and accessed account and billing information for all accounts created before October 30. [1]
  • Cursor says an access key it had issued to Fireworks was obtained by an attacker, who copied data from a read-only storage bucket shared with Fireworks. A tampered extension was then available for approximately 11 hours, reaching at most 5,000 users. [2][6]
  • Notion says Fireworks notified it of an incident affecting fewer than 1% of workspaces, involving unattributable AI chat sessions. Notion disconnected from Fireworks as of November 3 and found that data was retained from the Fireworks endpoints it used. [3]
  • Uber's letter says a service provider notified it on October 9 that its internal credentials were compromised and used to reach Uber's account with that provider. Press identified the provider as Fireworks and reported nearly 150,000 drivers notified. [4][5]

How it works

The attack as a living map, in kill-chain order from the first foothold to impact. Point at a step to light its wiring, click to pin its story.

at risk
  • entry
  • next step
  • impact

Read the attack chain

The threat on the left, each step in order, the people at risk on the right: point at a step to light its wiring, click to pin its story here.

00the attack chain
  • entry
  • next step
  • impact

Tap a node to read its story.

Step by step

  1. Steal vendor credentials

    Fireworks reports that stolen internal credentials, and later a compromised third-party cloud provider, gave the attacker a way into its systems. [1]

  2. Reach secrets and shared storage

    Fireworks says customer secrets such as API keys and tokens were captured in some accounts. Cursor says a key it issued to Fireworks opened a shared storage bucket. [1][2]

  3. Use secrets against customers

    SecurityWeek reports the bucket contained unredacted credentials that opened SaaS tools used by Cursor. Uber's letter says the vendor's credentials were used to access Uber's account with the vendor. [4][6]

  4. Abuse trusted distribution

    Cursor says the attacker published tampered copies of a Claude Code extension that were not present in the Open VSX marketplace source. Uninstalling alone may not be enough. [2][6]

  5. Monetize LLM access

    Fireworks links the activity to a financially motivated group that sells LLM tokens obtained through unauthorized access to illicit routing gateways. [1]

Who is at risk

Any organization that sends prompts, files, datasets or credentials to an AI inference or model hosting provider inherits that provider's security.

  • Customers whose API keys, tokens or other secrets are stored in a vendor platform, since Fireworks says removing a stored secret does not invalidate the underlying credential. [1]
  • Organizations that rely on a contractual zero data retention promise without testing it, since Notion found data retained from the endpoints it used. [3]
  • Employers and platforms holding personal data that a vendor can reach, as the Uber notices show. [4]
  • Developer teams that install tools through extension marketplaces and issue shared keys to partners. [2]

Sectors in scope

  • Organizations sending data to AI inference and model hosting providers
  • Software and AI product companies with vendor-held data
  • Employers and platforms whose personal data sits with a service provider
04What changed

What changed since the last edition

Fall/Winter 2026/2027 Edition5 changes

  1. November 9: Fireworks widened its disclosure to resource metadata, billing information and, for certain customers, a subset of incomplete model weights and datasets. It said payment card numbers are not stored by Fireworks.

    Source 1
  2. November 17: Fireworks stated that the earlier and later activity are two separate incidents and that both are contained and remediated.

    Source 1
  3. Cursor moved all inference traffic off Fireworks, deactivated the key it had issued and rotated every exposed credential it found.

    Source 2
  4. Notion disconnected from Fireworks, disabled its Insights feature during the investigation and announced an audit of critical vendors for data minimization and zero data retention practices.

    Source 3
  5. Week of November 16: Uber's driver notices and state filings put a count on the downstream personal data exposure.

    Source 5

What to do now

In priority order, highest impact first.

  1. Do firstInventory every AI vendor and every API key, token and connector that reaches one.

    You cannot rotate or cut off access you cannot list; Fireworks customers needed to find and replace keys quickly. [1]

  2. Scope each key to one purpose, set an owner and expiry, and rotate on a schedule.

    Narrow, short-lived keys limit what a vendor-side theft can open; Cursor's single issued key reached a shared bucket. [2]

  3. When a vendor reports a breach, rotate third-party credentials at the issuer, not only inside the vendor platform.

    Fireworks warns that removing a stored secret alone does not invalidate the underlying credential. [1]

  4. Minimize what you send to inference providers and keep secrets and personal data out of prompts.

    Notion's guidance tells users to keep secrets out of chats and documents, and its transcripts included whatever users typed. [3]

  5. Verify zero data retention claims with the vendor and by testing, and check what each feature stores.

    Notion learned that data was retained from the Fireworks endpoints it used, and its commitment does not cover stored-history features. [3]

  6. Add breach notification timelines and subprocessor disclosure to AI vendor contracts.

    Uber learned of the compromise from its provider on October 9, and Uber said it had alerts enabled but none triggered. [4][5]

  7. Log vendor API use and alert on unfamiliar keys, users, jobs, datasets and unusual traffic.

    Fireworks and Notion both advise reviewing audit and access logs for unrecognized activity. [1][3]

  8. Write an offboarding runbook that disconnects data flows, revokes keys and confirms deletion.

    Uber severed data connections, Cursor deactivated its key and Notion disconnected and reported data deleted from Fireworks systems. [2][3][4] If you want help with this, Z7 offers vendor risk review and Managed Private AI (/ai-services/managed-private-ai/) for keeping inference data under your control.

Sources

Every number and claim in this brief traces to a source below. Each source opens in a new tab at the publisher.

  1. [1]
    Fireworks security bulletins (October 10, November 9 and November 17, 2026) (opens in a new tab) Fireworks AI · October 10, November 9 and November 17, 2026 · fireworks.ai
  2. [2]
    Security incident update (opens in a new tab) Cursor · As published by Cursor, November 2026 · cursor.com
  3. [3]
  4. [4]
    Uber notifies drivers of data breach affecting nearly 150,000 people (opens in a new tab) BleepingComputer · November 2026 · bleepingcomputer.com
  5. [5]
  6. [6]
    Cursor Supply Chain Attack Started at Fireworks AI (opens in a new tab) SecurityWeek · November 16, 2026 · securityweek.com

Z7 Weekly Intelligence

We aim for one email a week: the threats that matter, new Z7 intelligence briefs and articles, and what to do about them. Unsubscribe anytime.

By subscribing, you agree to our Terms of Use. Our Privacy Policy explains how we use your email.

What does this mean for your security?

Bring your questions about exposure, defenses and cost. Talk with our team about what applies to your environment and where to start.

Ask Zeus AI assistant