Executive Summary
An Uber data breach that ran through AI vendor Fireworks AI exposed images of US drivers’ licences, according to notices Uber filed with state regulators on 10 November 2026. Uber says an attacker used Fireworks’ compromised internal credentials on 7 October to reach a cloud storage environment Uber had built for the vendor’s work. Fireworks alerted Uber on 9 October, four days later Uber confirmed that drivers’ personal data was among the files accessed. Filings for Iowa, South Carolina and Rhode Island alone cover more than 8,000 people. Uber has given no national total and says it has found no misuse of the data so far.
How Fireworks Credentials Led to the Uber Data Breach
Uber’s notice to the Iowa Attorney General doesn’t name the vendor. It says a service provider reported that an outsider had compromised the provider’s internal credentials and used them to enter Uber’s account there. Uber cut its data connections. An Uber spokesperson later confirmed the provider was Fireworks AI which sells developers access to open AI models.
The licence files sat in storage Uber built specifically for the vendor’s work and monitored with its own tools. Alerting was on. It didn’t help. The notice says “no alerts were triggered” because the attacker used valid credentials and data flows from the vendor’s compromised system.
Uber says the credentials reached no other Uber systems.
Fireworks spotted the misuse of its internal credentials on 6 October and began containment that day, according to its first security bulletin. That bulletin, last updated on 10 October, said Fireworks had found no evidence of access to personal information “within the Fireworks security perimeter or control”.
Licence Images, Home Addresses and No National Total
The files held images of driver’s licences plus text extracted from them, name, address, date of birth and licence number. Uber’s Iowa filing counts about 2,999 residents and its letter to drivers lists about 1,873 in Rhode Island. South Carolina’s Department of Consumer Affairs lists 3,430. California’s breach listing gives 7 October as the breach date but no count. Drivers have 90 days from their letter to enrol in free credit monitoring through Cyberscout.
Fireworks Ties the Intrusion to LLMjacking
Fireworks widened its account in a 9 November update. Forensic work with Palo Alto Networks Unit 42 found that attackers reached account and billing data and, for a limited set of customers, secrets, datasets and incomplete model weights. Fireworks links the activity to a financially motivated group selling stolen access to large language models, a practice known as LLMjacking. A second intrusion on 24 October came through a cloud provider hosting Fireworks research machines. The Uber data breach predates it by more than two weeks.
Cursor says a key it had issued to Fireworks let the attacker copy data from a shared storage bucket. Notion says AI chat transcripts from under 1% of its workspaces were exposed.
Uber’s Record on Driver Data
In its annual report for 2021, Uber said a 2016 breach exposed the driver’s licence numbers of about 600,000 drivers. That case ended in a $148 million settlement in 2018 that required Uber to maintain a comprehensive information security programme.
In Europe, the Dutch data protection authority fined Uber €290 million in 2024 for sending EU drivers’ data, including identity documents, to the United States without adequate transfer safeguards. The EDPB case summary lists the Swedish, Danish, Finnish and Norwegian authorities among those concerned.
Still Unanswered
Uber hasn’t said how many drivers it is notifying in total. Nor has it said what work Fireworks did with licence images or whether drivers outside the United States had records in the same environment. Fireworks’ bulletins give no account of how its internal credentials were first stolen.
Valid Credentials, Silent Alerts and a GDPR Window
Uber’s monitoring stayed silent because the attacker arrived with credentials and data flows Uber had approved for its vendor. Fireworks raised the alarm two days after the files were reached. The 2024 Dutch decision shows Uber has stored EU drivers’ identity documents on US servers before. If any EU driver records sat in the Fireworks environment, the GDPR’s 72-hour window to notify the lead authority, counted from Uber’s 13 October finding, ran out on 16 October. Uber has not said whether any did.
References
- Uber notice of security incident
- Data breach report: Uber Technologies, Inc.
- Security breach notices
- Fireworks October 2026 security incident
- Update on October 2026 security incident
- An update on our recent security incident
- Notice about the Fireworks AI incident
- Uber Form 10-K 2021
- $148 million Uber settlement, 2018
- Dutch SA imposes a fine of 290 million euro on Uber
This post is also available in:
