01
Cursor says a key exposed at Fireworks AI let attackers copy agent traces and reach other internal systems
In an update dated November 13, 2026, Cursor said the October breach started with an access key issued to Fireworks AI, which Fireworks had exposed. The attacker used it to copy a storage bucket holding historical coding-agent traces from users who had not turned on Privacy Mode; Cursor puts this at fewer than 0.05% of users. Some traces contained API credentials, which BleepingComputer reports opened access to further Cursor tools, including archived non-production code, some support emails and credentials customers had shared with support. Cursor says fewer than 0.01% of customers had credentials exposed, that the last attacker activity was blocked on November 1, and that Privacy Mode data, production systems and customer repositories were not affected. This adds the root cause to the malicious Claude Code extension copy reported earlier.
What it means for you
If your team uses Cursor, check whether an admin received a list of exposed credentials and rotate those keys, and never paste secrets into support tickets or agent sessions. Where coding agents handle sensitive code, turn on the tool's privacy or zero-retention setting.