mcp-remote: OS Command Injection via OAuth Endpoint
The fix is more than a year old, but version-pinned MCP client configs and stale npx caches can keep a vulnerable mcp-remote alive, so confirm the version and move on.
Must act: Anyone whose Claude Desktop, Cursor, Windsurf or other MCP client config launches mcp-remote at a version below 0.1.16, especially on Windows.
Can relax: Users who run mcp-remote 0.1.16 or later, or who don't use mcp-remote at all.
- Grep MCP client configs (claude_desktop_config.json, .cursor/mcp.json, etc.) for `mcp-remote` and note any pinned version.
- Change pins to `mcp-remote@latest` or an explicit version at or above 0.1.16.
- Clear stale npx copies (`npm cache clean --force`, or delete the `_npx` directory under the npm cache) so an old cached build isn't reused.