November 22, 2026

Uber Data Breach Exposes Personal Information of Thousands of Drivers Following Third-Party Vendor Compromise

A significant security breach has compromised the personal information of thousands of Uber drivers across the United States, following a targeted attack on one of the ride-hailing giant’s third-party software suppliers. The incident, which involved the theft of sensitive documents including driver’s license details, underscores the persistent vulnerabilities inherent in modern, interconnected corporate supply chains.

According to a mandatory data breach notification filed with the Iowa Attorney General’s office, the cyberattack was facilitated through the use of compromised access credentials. These credentials belonged to one of Uber’s service providers and were utilized by unauthorized third parties to gain entry into a specific cloud storage environment. While Uber maintains rigorous oversight of its digital infrastructure, the nature of the attack allowed the perpetrators to bypass standard detection protocols by masquerading as legitimate users.

The breach has sparked concerns regarding the security of driver data and the broader implications of "LLMjacking," a burgeoning trend in cybercrime where attackers seek to exploit enterprise artificial intelligence capacity for financial gain. As investigations continue, the full scale of the exposure remains to be seen, though early disclosures from various state regulators suggest a widespread impact.

The Mechanics of the Breach

The legal filing, submitted on Uber’s behalf by Amelia Gerlicher, a Privacy and Data Security Partner at Ashurst Perkins Coie, provides a detailed look at how the security failure occurred. The compromised environment was not a general-purpose server but a specialized cloud storage area designed specifically to facilitate the work of the service provider in question.

Crucially, the report notes that this environment was subject to Uber’s internal cloud security management processes and was under the direct oversight of Uber’s Cloud Security team. Despite these safeguards, the attackers were able to navigate the system without triggering security alarms. This was largely because the unauthorized third party utilized valid, albeit compromised, credentials.

“The environment had alerting enabled, but because the unauthorized third party used valid credentials and data flows enabled by the compromise on the service provider’s system, no alerts were triggered,” Gerlicher explained in the disclosure. This highlights a common and sophisticated challenge in modern cybersecurity: the difficulty of distinguishing between a legitimate employee performing their duties and a malicious actor using stolen identity markers.

Uber has clarified that the breach was contained within this specific silo. The compromised credentials did not grant the attackers access to Uber’s broader internal systems, core codebase, or the primary databases that house passenger information. However, for the drivers whose data was stored in that specific environment, the breach was exhaustive.

According to the official disclosure notice, the attackers successfully exfiltrated high-value personal information. The stolen data includes images of driver’s licenses and extracted text data, encompassing full names, residential addresses, dates of birth, and driver’s license numbers. The theft of physical images of licenses is particularly concerning, as these documents are often used as primary forms of identification for a variety of legal and financial transactions, increasing the risk of identity theft for those affected.

Assessing the Scale of Impact

Determining the exact number of individuals affected by the breach is an ongoing process as state-level disclosures continue to trickle in. Based on official information currently available from a range of U.S. states, including Iowa, Texas, and South Carolina, it is confirmed that a minimum of 16,236 Uber drivers have had their information stolen.

However, security experts and industry observers expect the true number to be significantly higher. Several of the most populous states, including California, New York, and Illinois—which represent some of Uber’s largest driver markets—have yet to confirm the specific number of affected residents. In many jurisdictions, data breach notification laws require companies to report the number of impacted individuals only after a thorough internal census, meaning the current figure likely represents only a fraction of the total victim count.

Uber has begun the process of notifying affected drivers, providing them with details on the nature of the breach and advice on how to protect their identities. For many drivers, the news is a distressing reminder of the risks associated with the digital gig economy, where the submission of sensitive personal documents is a prerequisite for employment.

What caused the Uber data breach?

The origin of the security lapse has been traced back to a specific link in Uber’s technological supply chain. Following an internal investigation, the company determined that the attack took place on October 7, 2026. The service provider involved disclosed the incident to Uber shortly thereafter, on October 9.

Industry reports and subsequent confirmations have identified the source of the breach as Fireworks AI. Fireworks AI is a prominent cloud provider that offers infrastructure for running and training open-source artificial intelligence models. As companies like Uber increasingly integrate AI into their operations—ranging from route optimization to automated document verification—they rely on specialized vendors like Fireworks AI to provide the necessary computational power and model management environments.

An Uber spokesperson confirmed the involvement of the vendor in a statement, noting that the notices sent to drivers were a direct result of the security incident at Fireworks AI. The spokesperson emphasized that the vendor had access to a limited subset of Uber data required for their specific AI-related tasks.

Fireworks AI has been transparent about the incident, publishing a security bulletin on October 9 that detailed the "unauthorized use of internal Fireworks credentials." The company’s internal monitoring first identified malicious activity on October 6, and they worked to notify impacted customers over the following three days.

According to Fireworks AI, the attackers managed to access a variety of metadata, including resource identifiers, display names, and creation timestamps. More critically, the breach extended to administrative and financial data, such as billing and shipping addresses, invoice and payment histories, account balances, and credit usage. In some instances, the attackers also accessed "incomplete model weights and datasets" for a limited number of customers, which could potentially reveal proprietary information about how certain AI tools are constructed or trained.

Who’s behind the Fireworks AI attack?

The motivation behind the attack appears to be rooted in a relatively new but rapidly growing sector of cybercrime. Fireworks AI stated that the evidence points to a financially motivated group of cybercriminals whose primary objective was to monetize unauthorized access to enterprise AI capacity.

This practice, known in the cybersecurity community as "LLMjacking," is analogous to "cryptojacking," where hackers hijack a victim’s processing power to mine cryptocurrency. In the case of LLMjacking, attackers seize control of expensive cloud-based GPU (Graphics Processing Unit) resources to run Large Language Models (LLMs) or other AI workloads. Given the high cost and high demand for AI compute power, stolen access to these resources has become a valuable commodity on the dark web.

While the primary goal may have been the theft of computational resources, the collateral damage—such as the theft of Uber’s driver data—remains a severe consequence. This incident serves as a stark example of how attacks on specialized AI infrastructure can lead to the exposure of traditional sensitive personal information.

Uber was not the only high-profile client affected by the Fireworks AI breach. The productivity and collaboration software vendor Notion has also publicly confirmed that it was caught in the wake of the incident. Notion utilized Fireworks AI for specific classification tasks designed to help users understand their own AI usage through a feature called "Insights."

In a security disclosure, Notion explained that they also used Fireworks as a general inference provider to serve open-weight models within their product suite. "The Insights feature has been disabled as we investigate this incident, and we are no longer serving open-weight models through Fireworks," the company stated. The decision to sever ties or suspend features illustrates the immediate operational impact that third-party security failures can have on even the most robust tech platforms.

The situation for Fireworks AI was further complicated by a subsequent security incident on October 24, 2026. In this second event, an attacker gained access to the company’s development environment through the compromise of a different third-party cloud hosting provider. During this window, the intruder ran an unauthorized workload and accessed additional customer data. Fireworks AI reported that this second attack was detected and remediated within the same day, but the back-to-back incidents have raised questions about the broader security posture of the AI service provider industry.

As Uber continues to work with regulators and law enforcement to address the fallout of the driver data theft, the incident highlights a growing challenge for the tech industry. As large enterprises become more dependent on a web of specialized AI and cloud vendors, their security is only as strong as the weakest link in that chain. For the thousands of drivers whose licenses are now in the hands of unauthorized actors, the breach is a reminder that in the age of AI, the risks to personal privacy are evolving just as quickly as the technology itself.