TLDR;
- Uber is notifying about 150,000 drivers that their personal information was accessed through a third-party vendor, which Uber confirmed to TechCrunch is Fireworks AI.
- Data involved per Uber: names, addresses, dates of birth, driver’s license numbers and images, and other government ID numbers.
- The attacker used valid compromised credentials.
- Uber cut its data connections to the vendor, is investigating, and offers free credit monitoring and fraud assistance.
- Affected drivers should enroll in the monitoring within 90 days of the letter date and watch for phishing and identity misuse.
Uber is a ride-hailing and delivery company. It disclosed the incident through breach notices filed with state attorneys general, including California, as reported by TechCrunch, SecurityWeek and Reuters. The notice is dated November 10, 2026 and did not name the vendor.
Uber later confirmed to TechCrunch that the vendor is Fireworks AI, a cloud platform for running and fine-tuning open source AI models. Fireworks has published its own security bulletins. Uber has not identified any misuse of the data so far, according to Reuters.
Status as of November 17, 2026: Uber’s investigation is ongoing.
What Happened
An unauthorized party used compromised credentials belonging to a third-party service provider to access data that Uber had shared with that provider. Uber says its alerts were enabled and none fired, because the credentials were valid. Fireworks attributes its incidents to a financially motivated cybercriminal group. TechCrunch reports that no known group has claimed the theft of the Uber data.
- October 6, 2026: Fireworks identified unauthorized use of internal credentials and began containment (Fireworks bulletin).
- October 7: the attacker used the credentials to access Uber data (SecurityWeek, citing Uber).
- October 9: the provider notified Uber, and Fireworks published its first bulletin.
- October 13: Uber determined the credentials had been used to access Uber data (Reuters).
- October 23 to 24: Fireworks reports a second event through a third-party cloud provider that hosted its R&D machines, with additional customer data impact.
- November 9: Fireworks published an update describing broader impact.
- November 13 and 16: TechCrunch reported that Uber confirmed Fireworks as the vendor, and updated the story.
Impact
Uber’s notices put the number of affected people at close to 150,000 drivers. The data types below come from Uber, as reported by SecurityWeek.
- Data involved: images of driver’s licenses, names, addresses, dates of birth, driver’s license numbers and other government-issued ID numbers.
- Count: 149,346 people according to a state attorney general filing (TechCrunch cites Oregon, SecurityWeek cites Texas). Reuters reports about 1,873 Rhode Island residents in the notice. TechCrunch says it is unclear whether the number will rise.
- Other Fireworks customers: TechCrunch reports that Notion and Cursor confirmed their data was also stolen.
- Fireworks reports impact to account and billing information, and for a limited set of accounts, secrets, datasets and incomplete model weights. It says payment card numbers were not affected.
- Uber states that the compromised credentials did not provide access to other Uber systems.
Company Response
Uber severed its data connections with the provider and opened an investigation. Fireworks engaged outside forensic specialists and has revoked and replaced credentials.
- Uber filed notices with state attorneys general, including California and Iowa, and notified drivers by letter.
- Uber offers free credit monitoring and fraud assistance through Cyberscout, a TransUnion company. Drivers must enroll within 90 days of the letter date (Reuters).
- Fireworks notified law enforcement and engaged Palo Alto Networks Unit 42 for forensic analysis.
- Fireworks restricted network paths, isolated affected systems, tightened access to data storage, and disabled self-serve dataset uploads and downloads while its investigation continues.
- Fireworks is notifying affected customers directly.
Recommended Actions
Driver’s license numbers, dates of birth and addresses can support identity fraud and targeted phishing. Uber’s notice directs affected drivers to the free monitoring service, and Fireworks lists steps for its customers. The remaining items are general guidance.
For affected individuals:
- Enroll in the free credit monitoring within 90 days of the date on your letter (Uber notice).
- General guidance: treat calls, texts and emails that mention Uber, your driver account or your license number as suspect, and contact Uber through its official app or website.
- Consider a fraud alert or credit freeze, and review your credit reports and account statements.
- If your license number is misused, report it to the issuing state agency.
For organizations that use Fireworks AI or share data with similar vendors:
- Replace revoked Fireworks API keys, and rotate the third-party credentials listed in your notice (Fireworks bulletin).
- Review activity for exposed credentials with the issuing providers, and check for unrecognized API keys, users, training jobs and datasets (Fireworks bulletin).
- General guidance: review which personal data is shared with vendors, scope vendor credentials narrowly, and alert on vendor credential use.
How Pentesting Can Help

The attacker in this case walked in on a vendor’s valid credentials and set off nothing. A continuous pentesting program is built for that exact scenario: it checks how far a single credential actually reaches and whether anyone notices when it is used outside its normal pattern, before a real incident proves the answer.
- Keep a live inventory of every application, API, and third-party connection, and record the data each one can touch.
- Test access scope regularly, so that vendor and service credentials stay pinned to the data they need.
- Test detection, so that alerts fire when valid credentials show up in unexpected ways.
- Retest after every release and every fix, not only on the annual cycle.
Astra runs continuous pentesting across web applications and APIs, combining automated scanning, autonomous AI pentesters, and an expert validation layer on top. The autonomous agents map your application, build a live threat model, and work through business logic flaws, broken access controls, and multi-step attack chains, including the kind that a stolen vendor credential would ride in on. Our API security testing carries its own inventory module that surfaces shadow, dormant, and undocumented endpoints. Every meaningful finding is validated by a human pentester before it reaches your dashboard, so the fix list reflects real exploitability.
Talk to our team if you want to see how the same engagement would look against your own vendor footprint.
References: Fireworks update (November 9, 2026)
FAQS
1. What happened in the Uber data breach?
Uber disclosed that approximately 150,000 drivers had their personal information accessed through compromised credentials belonging to its third-party vendor, Fireworks AI. The incident involved unauthorized access to data shared between Uber and the vendor.
2. What information was exposed in the Uber breach?
The exposed information includes drivers’ names, addresses, dates of birth, driver’s license numbers, images of driver’s licenses, and other government-issued identification numbers. This information could potentially be misused for identity theft, fraud, and targeted phishing attacks.
3. What should affected Uber drivers do?
Affected drivers should enroll in Uber’s free credit monitoring and fraud assistance program within 90 days of receiving their notification letter. They should also monitor financial accounts, review credit reports, and remain cautious of suspicious messages requesting personal information.
4. How did the Uber data breach happen?
The attacker accessed Uber’s data through valid but compromised credentials belonging to Fireworks AI, a third-party vendor. Because the credentials were legitimate, Uber’s security alerts did not trigger, highlighting the risks of excessive vendor access and insufficient credential monitoring.



