Cursor Security Incident Update Published
Is it fixed? Yes.
Resolved after 2 d 1 h. First reported Nov 14, 13:38 UTC, resolved Nov 16, 15:38 UTC.
What happened
Cursor published updates regarding a recent security incident affecting their platform, impacting users of the service.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on Hacker News thread
Cursor - An update on our recent security incident
Source - Status changed
Status changed: investigating → resolved (no new reports for 48h).
Evidence
3 reports · 3 HNShow
- [1]HN First reportCursor - An update on our recent security incident(opens Hacker News thread in a new tab)
by dsr12 5upvotes 0comments
- [2]HNAn update on Cursor's recent security incident(opens Hacker News thread in a new tab)
by nreece 1upvotes 0comments99% match
- [3]HNCursor: An update on our recent security incident(opens Hacker News thread in a new tab)
by drodio 2upvotes 0comments100% match
FAQ
What happened in the Cursor outage?
Cursor published updates regarding a recent security incident affecting their platform, impacting users of the service.
What is affected by the Cursor outage?
Cursor.
When did the Cursor outage start and end?
It started Nov 14, 13:38 UTC and was resolved Nov 16, 15:38 UTC, after 2 d 1 h.
How do I get alerts for Cursor?
Subscribe to the Cursor RSS feed for every new Cursor incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Cursor is down. Cursor feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 3 reports from 1 independent source.