Vulnerability in Cursor (CVE-2026-50549)
Summary
Vulnerability in Cursor (CVE-2026-50549). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.0 or later.
Original description
The description as published by the source.
Cursor is a code editor built for programming with AI. Prior to 3.0, Cursor runs agent terminal commands in a sandbox by default. Before a Write, the agent canonicalizes the target path to confirm it stays inside the workspace, but when canonicalization fails it falls back to the original path and writes without approval. A malicious agent can create an in-workspace symlink that points outside the workspace and force canonicalization to fail — either because the target does not exist or because read permission is removed from the path — so the agent writes through the symlink to an arbitrary location without approval. A malicious agent could write arbitrary files outside the workspace under the user's privileges. This enables non-sandboxed Remote Code Execution — for example by overwriting the cursorsandbox helper so later commands run unsandboxed — with no user interaction beyond a benign prompt. This vulnerability is fixed in 3.0.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50549 has been found in Cursor.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade Cursor to 3.0 or later.
If unsure, ask your IT team or search "Cursor CVE-2026-50549" on the vendor's site.
CVE-2026-50549 (Cursor) — CWE-59 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-59) exists in Cursor.
Check the vendor advisory for the affected versions of Cursor.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Cursor' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Cursor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Cursorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Cursor to 3.0ステージング環境で 3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。