Edition of Sunday 15 November 2026

Cursor - An update on our recent security incident

Comments on “Cursor - An update on our recent security incident”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Cursor's post-incident report traces the breach to an access key it issued to vendor Fireworks, which the vendor exposed. The attacker copied coding agent traces, some with unredacted credentials, reached internal SaaS tools, and on October 29 placed a fake Claude Code extension in the marketplace cache. Cursor says at most 5,000 users may have received it over about 11 hours, and it considers the incident contained. Most figures are Cursor's own and unverified. The lesson for builders: vendor-shared data and credentials in logs are supply-chain risks.

Read the original at cursor.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 7 of 62 with a score of 0.69. The panel rated it highest on new information (0.85) and reader interest (0.83), lowest on audience breadth (0.57). Placed No. 7, No. 9 by score alone: close to “Phala Confidential AI Compromised”, No. 5 on Thursday 12 November 2026 (−0.009). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Detailed post-incident disclosure of a supply-chain attack on a VS Code extension marketplace and exposed credentials; high security relevance, practical lessons for builders, with some self-serving framing and limited technical depth.}
AI judgeJudge 3gpt-5.6-luna
A detailed first-party incident report covering credential exposure, supply-chain compromise, malicious VS Code extension distribution, scope, customer impact, and remediation. It is actionable and well-supported, though specific to one platform and largely retrospective.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.69total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.65
  • Reader interest0.83
  • Audience breadth0.57
  • Practical relevance0.74
  • Substantiated0.73
  • Technical depth0.66
  • New information0.85
  • Counts against: Promotional0.08
  • Counts against: Overclaim0.14

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.620.600.720.650.12+0.24+0.155
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.790.800.900.830.11+0.26+0.216
Audience breadthHow many people who build technology does it concern?0.350.670.680.570.33+0.13+0.074
Practical relevanceHow useful is it to someone who builds software or tech products?0.720.700.800.740.10+0.22+0.163
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.600.670.930.730.33+0.05+0.037
Technical depthHow technically substantive is it?0.690.600.680.660.09+0.05+0.033
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.810.800.930.850.13+0.05+0.042
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.100.100.030.080.07−0.19−0.015
OverclaimDo the headline or conclusions claim more than the body supports?0.140.200.080.140.12−0.11−0.015
Sum of contributions+0.689
Claim-check penalty0.000
Total, as published0.690

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #7 on Rubric, 15 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-15/7/"><img src="https://rubric.hrih.si/badge/2026-11-15/7.svg" alt="Ranked #7 on Rubric, 15 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: 1 matches source · 6 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenNumber

    Fewer than 0.01% of Cursor customers had API credentials exposed in the traces copied from the storage bucket.

    The article gives no link or citation for it.

    The article says

    “less than 0.01% of customers had API credentials exposed”

    The source says

    No source to compare with.

  2. Couldn’t checkCausal conclusion

    Fireworks exposed an access key issued by Cursor, which the attacker used to copy data from a read-only storage bucket shared with Fireworks.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “The key was exposed by Fireworks, and the attacker used it to copy data from a read-only storage bucket we used to share data with them”

    The source says

    No passage could be compared.

    Source cited by the article: fireworks.ai/security/bulletins

  3. No source givenDate

    On October 29, the attacker placed malicious, unauthorized copies of Anthropic's Claude Code extension on the cache serving the Cursor VS Code extension marketplace, using a stolen credential.

    The article gives no link or citation for it.

    The article says

    “On October 29, using a stolen credential from the exposed data from our internal system, the attacker placed malicious, unauthorized copies of Anthropic's Claude Code extension”

    The source says

    No source to compare with.

  4. No source givenNumber

    At most 5,000 users who requested specific cached versions of the extension on October 29 potentially received the malicious build.

    The article gives no link or citation for it.

    The article says

    “At most 5,000 users who requested specific cached versions of the extension on October 29 potentially received the malicious build”

    The source says

    No source to compare with.

  5. No source givenNumber

    The malicious extension was available for approximately 11 hours before Cursor removed it.

    The article gives no link or citation for it.

    The article says

    “It was available for approximately 11 hours before we removed it”

    The source says

    No source to compare with.

  6. Matches sourceVersion

    The tampered versions were Anthropic.claude-code 2.1.312 and 2.1.313 from the Cursor VS Code extension marketplace.

    The cited source says the same thing.

    The article says

    “tampered version Anthropic.claude-code 2.1.312 or 2.1.313”

    The source says

    “a specific extension in the Cursor VS Code Extension Marketplace: Anthropic.claude-code version 2.1.312 and 2.1.313 for Windows and MacOS”

    Source cited by the article: cursor.com/blog/claude-code-extension-security-notice

  7. No source givenDate

    The last attacker activity Cursor saw was on November 1, and it was blocked.

    The article gives no link or citation for it.

    The article says

    “The last attacker activity we have seen was on November 1, and it was blocked”

    The source says

    No source to compare with.

  8. No source givenNumber

    For users not using Privacy Mode, coding agent traces were exposed for fewer than 0.05% of users.

    The article gives no link or citation for it.

    The article says

    “coding agent traces were exposed for fewer than 0.05% of users”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 6 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:46 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Cursor - An update on our recent security incident”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.