CVE-2026-50549

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
46.3%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jul 12, 2026
Patch available. Sources: github.
github Patch Available

Cursor Desktop sandbox escape via symlink and failed path canonicalization · Advisory · cursor/cursor · GitHub

https://github.com/cursor/cursor/security/advisories/GHSA-3v8f-48vw-3mjx

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 49× in last 7d / 121× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 121 total refreshes for this CVE.

  1. 2026-07-13 01:28 UTCEG score recompute
  2. 2026-07-12 21:15 UTCEG score recompute
  3. 2026-07-12 16:31 UTCEG score recompute
  4. 2026-07-12 12:18 UTCEG score recompute
  5. 2026-07-12 08:05 UTCEG score recompute
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-12 03:51 UTCEG score recompute
  8. 2026-07-11 23:38 UTCEG score recompute
  9. 2026-07-11 19:25 UTCEG score recompute
  10. 2026-07-11 15:12 UTCEG score recompute
  11. 2026-07-11 10:54 UTCEG score recompute
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 06:41 UTCEG score recompute
  15. 2026-07-11 02:28 UTCEG score recompute
  16. 2026-07-10 22:15 UTCEG score recompute
  17. 2026-07-10 18:02 UTCEG score recompute
  18. 2026-07-10 13:48 UTCEG score recompute
  19. 2026-07-10 09:35 UTCEG score recompute
  20. 2026-07-10 05:22 UTCEG score recompute
  21. 2026-07-10 01:07 UTCEG score recompute
  22. 2026-07-09 20:53 UTCEG score recompute
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 16:38 UTCEG score recompute
Show 75 more
  1. 2026-07-09 12:09 UTCEG score recompute
  2. 2026-07-09 07:57 UTCEG score recompute
  3. 2026-07-09 03:42 UTCEG score recompute
  4. 2026-07-08 23:29 UTCEG score recompute
  5. 2026-07-08 19:17 UTCEG score recompute
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-08 15:03 UTCEG score recompute
  9. 2026-07-08 10:50 UTCEG score recompute
  10. 2026-07-08 06:37 UTCEG score recompute
  11. 2026-07-08 02:24 UTCEG score recompute
  12. 2026-07-07 22:11 UTCEG score recompute
  13. 2026-07-07 17:59 UTCEG score recompute
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:45 UTCEG score recompute
  17. 2026-07-07 09:33 UTCEG score recompute
  18. 2026-07-07 05:19 UTCEG score recompute
  19. 2026-07-07 01:05 UTCEG score recompute
  20. 2026-07-06 20:52 UTCEG score recompute
  21. 2026-07-06 16:29 UTCEG score recompute
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 12:12 UTCEG score recompute
  24. 2026-07-06 07:58 UTCEG score recompute
  25. 2026-07-06 03:36 UTCEG score recompute
  26. 2026-07-06 02:23 UTCEPSS rescore
  27. 2026-07-05 23:22 UTCEG score recompute
  28. 2026-07-05 19:09 UTCEG score recompute
  29. 2026-07-05 14:56 UTCEG score recompute
  30. 2026-07-05 10:43 UTCEG score recompute
  31. 2026-07-05 06:30 UTCEG score recompute
  32. 2026-07-05 02:30 UTCEPSS rescore
  33. 2026-07-05 02:17 UTCEG score recompute
  34. 2026-07-04 22:04 UTCEG score recompute
  35. 2026-07-04 17:50 UTCEG score recompute
  36. 2026-07-04 13:35 UTCEG score recompute
  37. 2026-07-04 09:20 UTCEG score recompute
  38. 2026-07-04 06:31 UTCEPSS rescore
  39. 2026-07-04 05:07 UTCEG score recompute
  40. 2026-07-04 00:51 UTCEG score recompute
  41. 2026-07-03 20:39 UTCEG score recompute
  42. 2026-07-03 16:26 UTCEG score recompute
  43. 2026-07-03 12:11 UTCEG score recompute
  44. 2026-07-03 07:29 UTCEG score recompute
  45. 2026-07-03 03:17 UTCEG score recompute
  46. 2026-07-02 23:04 UTCEG score recompute
  47. 2026-07-02 18:51 UTCEG score recompute
  48. 2026-07-02 14:38 UTCEG score recompute
  49. 2026-07-02 10:26 UTCEG score recompute
  50. 2026-07-02 06:13 UTCEG score recompute
  51. 2026-07-02 01:59 UTCEG score recompute
  52. 2026-07-01 21:46 UTCEG score recompute
  53. 2026-07-01 17:34 UTCEG score recompute
  54. 2026-07-01 15:07 UTCEPSS rescore
  55. 2026-07-01 13:18 UTCEG score recompute
  56. 2026-07-01 09:05 UTCEG score recompute
  57. 2026-07-01 04:51 UTCEG score recompute
  58. 2026-07-01 00:38 UTCEG score recompute
  59. 2026-06-30 23:22 UTCEPSS rescore
  60. 2026-06-30 20:25 UTCEG score recompute
  61. 2026-06-30 16:11 UTCEG score recompute
  62. 2026-06-30 11:59 UTCEG score recompute
  63. 2026-06-30 07:44 UTCEG score recompute
  64. 2026-06-30 03:31 UTCEG score recompute
  65. 2026-06-29 23:19 UTCEG score recompute
  66. 2026-06-29 19:06 UTCEG score recompute
  67. 2026-06-29 14:53 UTCEG score recompute
  68. 2026-06-29 14:06 UTCEPSS rescore
  69. 2026-06-29 14:06 UTCEPSS rescore
  70. 2026-06-29 10:39 UTCEG score recompute
  71. 2026-06-29 06:27 UTCEG score recompute
  72. 2026-06-29 02:13 UTCEG score recompute
  73. 2026-06-28 22:00 UTCEG score recompute
  74. 2026-06-28 17:47 UTCEG score recompute
  75. 2026-06-28 14:07 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50549?
CVE-2026-50549 is a critical vulnerability published on June 25, 2026. 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…
When was CVE-2026-50549 disclosed?
CVE-2026-50549 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50549 actively exploited?
CVE-2026-50549 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50549?
CVE-2026-50549 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-50549?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50549, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50549

Explore →

Is Your Infrastructure Affected by CVE-2026-50549?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs