MCP Install Deeplink Did Not Show Arguments on User-Dialog
CVE-2025-54133 · GHSA-r22h-5wp2-2wfv · published 2025-08-01
- Severity
- Medium
- CVSS score
- Not scored
- Chance of exploitation (EPSS)
- Not scored
- Fixed in
- 1.3
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
If a user clicks a malicious deeplink, then examines the installation dialog (which did not show the arguments, but does show the command itself) and clicks through, the full command including the arguments will be executed on the machine.
Upgrade cursor to 1.3 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Displayed arguments in installation dialog.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| cursor | App | 1.17 | 1.3 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalCursor Desktop sandbox escape via agent-controlled working directorycursor
- CriticalCursor Desktop sandbox escape via symlink and failed path canonicalizationcursor
- HighSandbox escape via tampered Python virtual environmentscursor
- HighSandbox escape via launching privileged containerscursor
- HighCursor Desktop sandbox escape via Claude hook configurationcursor
- HighSandbox escape via Git hookscursor
The impact, patch and workaround text comes from the advisory, shortened (published by Cursor). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.