@arikusi/deepseek-mcp-server: Missing Authentication on Self-Hosted HTTP MCP Endpoint
CVE-2026-55605 · GHSA-72f3-6w86-7rv3 · published 2026-08-25 · updated 2026-10-01
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- 0.52%
- Fixed in
- 1.8.0
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
In self-hosted HTTP deployments, any host with network access to port 3000 can establish an authenticated-equivalent MCP session and invoke built-in MCP tools without supplying credentials. This was verified end-to-end for session establishment, tool enumeration, and execution of the local deepseeksessions tool. deepseekchat is exposed through the same unauthenticated MCP session, and its handler routes requests through the server-side DeepSeek client. That means a deployment using a valid server-side DEEPSEEKAPIKEY places billable DeepSeek operations behind an unauthenticated endpoint.
Upgrade @arikusi/deepseek-mcp-server to 1.8.0 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.
Require authentication in self-hosted HTTP mode before MCP session creation. At minimum, pass an authProvider to createMcpExpressApp at transport-http.ts:17 or place equivalent authentication middleware / a reverse proxy in front of /mcp so unauthenticated clients never reach the initialize branch: For deployments that only need local access, bind to 127.0.0.1 instead of 0.0.0.0 in both createMcpExpressApp and app.listen (transport-http.ts:17 and :107) as a defence-in-depth measure. Upstream docker-compose.yml currently publishes 3000:3000; changing that to 127.0.0.1:3000:3000 would reduce inadvertent exposure on multi-user or server hosts.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @arikusi/deepseek-mcp-server | npm | >= 1.4.2, < 1.8.0 | 1.8.0 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- High@arikusi/deepseek-mcp-server has an Authorization Bypass Through User-Controlled Key@arikusi/deepseek-mcp-server
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.