---
title: Cursor traces its October breach to a key it gave Fireworks AI: stolen coding-agent traces held unredacted credentials, which led to SaaS tools, support data and the fake Claude Code extension | ctxsec
url: https://ctxsec.com/items/cursor-nov-13-incident-update-fireworks-exposed-key-agent-traces-credentials-malicious-claude-code-extension
description: "Cursor's Nov 13 update says an attacker obtained an access key Cursor had issued to Fireworks (exposed by Fireworks) and used it to copy a read-only bucket of coding-agent traces, mostly from 2025, from sessions not in Privacy Mode that Cursor was permitted to use for training. A small number of traces held unredacted credentials (less than 0.01% of customers had API credentials exposed). With those, the attacker reached select SaaS tools Cursor uses and accessed archived non-production source repos (some with business contact info), limited support data and email, product usage metrics and contact details, summaries of some agent conversations, and some credentials users had sent to Cursor support. On Oct 29, using a stolen credential, the attacker put tampered copies of Anthropic's Claude Code extension on the cache serving Cursor's VS Code extension marketplace for about 11 hours; at most 5,000 users may have received it. Cursor says traces were exposed for fewer than 0.05% of non-Privacy-Mode users, all notified directly; production systems, the Cursor app and its updates (no release signing keys exposed), other extensions and customer repos were not affected."
status: "official (Cursor incident update, Nov 13, 2026); Cursor says contained, last attacker activity Nov 1"
published: 2026-11-14
---

> Cursor's Nov 13 update says an attacker obtained an access key Cursor had issued to Fireworks (exposed by Fireworks) and used it to copy a read-only bucket of coding-agent traces, mostly from 2025, from sessions not in Privacy Mode that Cursor was permitted to use for training. A small number of traces held unredacted credentials (less than 0.01% of customers had API credentials exposed). With those, the attacker reached select SaaS tools Cursor uses and accessed archived non-production source repos (some with business contact info), limited support data and email, product usage metrics and contact details, summaries of some agent conversations, and some credentials users had sent to Cursor support. On Oct 29, using a stolen credential, the attacker put tampered copies of Anthropic's Claude Code extension on the cache serving Cursor's VS Code extension marketplace for about 11 hours; at most 5,000 users may have received it. Cursor says traces were exposed for fewer than 0.05% of non-Privacy-Mode users, all notified directly; production systems, the Cursor app and its updates (no release signing keys exposed), other extensions and customer repos were not affected.

[← Context & Harness Attacks](/context) · [markdown](/items/cursor-nov-13-incident-update-fireworks-exposed-key-agent-traces-credentials-malicious-claude-code-extension.md)

official (Cursor incident update, Nov 13, 2026); Cursor says contained, last attacker activity Nov 1

2026-11-14 3:41 PM ET

### Cursor traces its October breach to a key it gave Fireworks AI: stolen coding-agent traces held unredacted credentials, which led to SaaS tools, support data and the fake Claude Code extension

- **The chain:** vendor-held key → training-data bucket → secrets pasted into agent sessions → SaaS tools → a credential that could write to the extension cache. No zero-day was involved, per Cursor.
- **Cursor's fixes:** moved all inference off Fireworks and cut its data access, rotated every exposed credential and, as a precaution, all internal ones, rebuilt the extension marketplace, restricted where service-provider credentials can be used, added secret scanning to repos and other internal data, redeployed production, and brought in external forensics.
- **If you used Cursor on Oct 29:** follow the Oct 29 notice for Anthropic.claude-code 2.1.312/2.1.313 (svc-telemetry key check); uninstalling alone may not be enough.
- **If you were notified:** rotate the keys listed in Cursor's email; any secret you pasted into an agent session or sent to support should be treated as exposed.
- **Still unknown:** whether any exposed customer key was misused, and absolute customer counts.

Sources: [Cursor: An update on our recent security incident (Nov 13, 2026)](https://cursor.com/blog/security-incident-update) · [Cursor: Security notice, malicious Anthropic.claude-code 2.1.312 and 2.1.313 (Oct 29-30, 2026)](https://cursor.com/blog/claude-code-extension-security-notice) · [BleepingComputer: Cursor confirms security breach led to malicious Claude Code extension (Nov 14, 2026)](https://www.bleepingcomputer.com/news/security/cursor-confirms-security-breach-led-to-malicious-claude-code-extension/) · [Fireworks AI: Update on October 2026 security incident (Nov 9, 2026)](https://fireworks.ai/security/bulletins/october-2026-security-incident-update)
