Cases › security breach › LR-2026-0873
Fireworks AI: October 23-24 breach via third-party cloud provider
- Who was hit
- Some Fireworks customers, whose billing information, resource metadata, and incomplete model weights and datasets were accessed
- Reported
- 10 Nov 2026
- Severity
- Moderate
- Attackers breached a third-party cloud provider and used it to access Fireworks development machines, crossing the boundary of Fireworks' systems.
- Attackers accessed resource metadata, billing information, and incomplete model weights and datasets for some customers. Payment card numbers were not reached because Fireworks does not store them.
- Fireworks says it detected the activity on the same day it occurred.
Source: BleepingComputer · 2 more
What was done
Fireworks revoked and replaced credentials and service accounts, restricted network pathways, isolated affected systems and tightened data access. It is working with Palo Alto Networks' Unit 42 to investigate scope.
Patched or fixed (Affected organisation) · Access revoked or keys rotated (Affected organisation) · Users or authorities notified (Affected organisation) · Other stated action (Affected organisation) · Access revoked or keys rotated (Affected organisation) · Other stated action (Affected organisation)
Fix reported: “Revoked and replaced credentials and service accounts, restricted unauthorized network pathways, isolated affected systems, and tightened access to data storage and analytics systems.” · Short-lived, scoped credentials
Risks AI system attacked or breached (54 incidents)
No source states: AI company and model, money lost or records, tools it had, company using the AI, sector.
Similar incidents
Evidence
- Cause a shared system was the path
Sources (3)
- Fireworks AI discloses new breach after cloud provider hack · BleepingComputer · 2026-11-10
- Fireworks AI admits a second breach, and this one reached customer models and billing data · Business Upturn · 2026-11-10
- Fireworks AI suffers second data breach, exposing Notion customer data · Crypto Briefing · 2026-11-12
Show every field, with its source and grade
What happened
Impact
Notes on gaps
Number of affected customers and records is not stated. Part of the summary sentence about the provider incident is paraphrased from the cited sentence.
LR-2026-0873 · version 6 · published 2026-11-13 after automatic checks; not yet checked field by field by a person