What happened
On November 9, 2026, Fireworks AI updated a security bulletin it first published on October 9. The earlier notice described misuse of internal credentials. The update says more happened. Fireworks says a third-party cloud provider that hosted its research and development machines had a security incident on October 23. On October 24, an unauthorized party used it to reach Fireworks development machines and run an unauthorized workload. Fireworks says it detected the activity that day and had not seen further successful access to the platform customers use as of October 25. The company says the affected internal application gave access to resource metadata, billing information (addresses, invoices, payment history, balances, credit usage) and, for certain customers, a subset of incomplete model weights and datasets. It says payment card numbers are not stored and were not affected. For a limited set of accounts, it also reports impact to stored secrets. Fireworks says it has found no impact to its Inference, Training SDK and Nexus services, which it describes as zero data retention by default. It has disabled self-serve dataset uploads and downloads for batch inference and dataset-based training while it investigates, and says the investigation is ongoing. Bloomberg Law reported that Fireworks is working with customers including Notion and Cursor, and that it has more than 10,000 customers. Fireworks has not named the cloud provider, and the reporting does not say how many customers were affected.
Why it matters for business owners
Most owners never sign a contract with a company like Fireworks directly. Their software vendor does, or a developer they hired does. The AI tools you use are often built on platforms you have never heard of, which in turn run on cloud providers you have also never heard of. That chain is where this incident happened. Fireworks was not breached at its front door. It was reached through a company it rented machines from. The second point is more practical. The exposed items included billing records and, for some accounts, datasets and unfinished model weights. If your team fine-tuned a model on customer or internal data, that data is an asset sitting on someone else's systems.
What owners should not misunderstand
Do not conclude that every AI platform is unsafe. Fireworks reports that its standard inference service keeps no prompts or outputs by default, and says it found no impact there. That is the company's statement from an ongoing investigation, so treat it as a claim to confirm, not a guarantee. Do not assume this only matters if you are a Fireworks customer. The pattern is general: platforms that store datasets, keys and trained models are worth more to an attacker than platforms that only pass requests through. Do not treat "we use a big name" as due diligence. Notion and Cursor are well-known companies, and both were named in connection with this incident. A recognizable logo on your vendor list says little about how well your vendor's own suppliers are protected. Do not assume deleting a stored key fixes it. Fireworks' customer guidance, as reported, says removing a stored secret does not cancel the underlying credential. The key has to be rotated with the company that issued it. And do not skip the billing side. An invoice history is useful to someone writing a convincing fake invoice.
The operational lesson
Your AI risk includes the vendors behind your vendors, and the things you chose to store with them. There are three separate exposures here: keys and secrets you gave a platform, data you uploaded to it, and records it holds about you. Each needs a different response, and most businesses cannot yet say which of them they have with any given AI vendor. The cheapest protection is to upload less and keep less. If a workflow works with data passed through at request time and not stored, a breach at the platform has less to take.
What a serious business should do next
List the AI platforms and tools your team and your outside developers use, including ones set up under a personal or team credit card. If you cannot produce the list, start there. For each, write down three things: what keys or secrets you gave it, what data you uploaded or stored there, and who at your company owns the account. Ask each important vendor in writing: do you store our prompts and uploads by default, can we turn storage off, which cloud providers host our data, and how and when would you tell us about an incident? A clear answer is a good sign. A vague one is information too. Know how to rotate. For every key an AI tool holds, find out where it was issued and how to replace it. Rotate on a schedule, and immediately when a vendor reports a problem. Keep a clean copy of anything you cannot afford to lose or leak. Do not make a hosted platform the only home for a fine-tuned model or a training dataset. Watch for follow-on fraud. If a vendor's billing records were exposed, brief your finance staff to verify unexpected invoices and address changes by a known phone number. When not to act: if you only use AI chat tools with no uploads, no stored keys and no fine-tuning, a short inventory is enough. A full review is for businesses that store data or models with AI platforms.
The Atlacis view
Atlacis helps owners slow down, understand the workflow, map the risk, choose the right tool or system, and avoid wasting money on AI decisions that do not match the business. Knowing what data lives with which AI vendor is part of that map, and it is usually missing. Sometimes the right answer is a different hosting arrangement, including keeping sensitive data on systems you control. Sometimes it is just uploading less. If you want help sorting which is which for your business, a short call can help.
The short version
- Fireworks AI says a breach at a third-party cloud provider let an attacker reach its development machines on October 24, 2026.
- Exposed items include billing records and, for a limited set of accounts, secrets, datasets and incomplete model weights.
- Fireworks reports no impact to its zero data retention services so far, and says its investigation is ongoing.
- List what keys, data and records each AI vendor holds for you, and who owns each account.
- Rotate keys at the issuer, upload less, and keep your own copy of anything you cannot lose.