Fireworks AI said on November 17 that it had identified two separate security incidents in 2026: one from August 3 to October 7 and another from October 23 to 30. The company said both were contained and remediated; Palo Alto Networks Unit 42 had completed its investigation of the first, while AprosSyber’s forensic investigation of the second was ongoing. Fireworks’ bulletin also distinguishes what happened in each incident. Separately, TechCrunch reported that Uber notified 149,346 people, while Notion said fewer than 1% of its workspaces were affected.

What the two incidents involved

For the August 3–October 7 incident, Fireworks said stolen company credentials and a vulnerability in one of its services were used to access secrets, model files and datasets belonging to a small number of customers.

The October 23–30 incident followed a different path. Fireworks said access to development machines hosted by a third-party cloud provider reached part of its production systems. Account and billing information for all accounts created before October 30 was accessed; for a small number of customers, datasets, models and/or secrets were accessed as well.

Fireworks said it does not store payment-card numbers and that they were not affected. The company described both incidents as contained and remediated, while the second investigation remained underway as of its November 17 bulletin.

What Uber, Notion and Cursor reported

TechCrunch reported that Uber notified 149,346 people about stolen personal information, including names, addresses, dates of birth and driver’s-license numbers. Uber did not tell TechCrunch how many of the people notified were drivers. Uber also said alerts did not trigger because the attackers used Fireworks’ internal credentials.

Notion said fewer than 1% of its workspaces were affected by exposure of Notion AI Insights chat transcripts. Most of the exposed transcripts could not be attributed to a person or workspace and contained no tool-call results. Notion said its own systems were not breached and no other workspace data or features were affected. It disconnected from Fireworks on November 3, deleted its data there on November 4, disabled Insights and stopped serving open-weight models through Fireworks.

PYMNTS reported that Cursor said an attacker used a Cursor access key issued to Fireworks, then a credential from exposed data, to publish a malicious extension. Cursor said it blocked the attacker’s last activity on November 1.

For affected Notion customers, review the impacted data securely in your workspace and rotate sensitive information, passwords, API keys or other credentials pasted into Notion AI during the incident period, as Notion recommends.