CVE-2026-55605: @arikusi/deepseek-mcp-server: Missing Authentication on Self-Hosted HTTP MCP Endpoint
The self-hosted HTTP transport of @arikusi/deepseek-mcp-server exposes POST /mcp without any authentication: createMcpExpressApp is called without an authProvider and no middleware guards the route, so any network-reachable client can issue an unauthenticated initialize request and obtain a valid MCP session identifier. In reproduced testing against commit 5e1302171e99, an unauthenticated client was able to initialize a session, enumerate tools, and invoke the local deepseek_sessions tool with no credentials. The same unauthenticated session also exposes deepseek_chat, whose handler uses the server-side DEEPSEEK_API_KEY when self-hosted deployments configure one.
This issue applies to self-hosted HTTP mode, not the separately documented hosted BYOK endpoint in README.md, which expects an Authorization: Bearer ... header. Upstream self-hosted container assets enable HTTP mode by default (Dockerfile) and publish port 3000 (docker-compose.yml).
References
- github.com/advisories/GHSA-72f3-6w86-7rv3
- github.com/arikusi/deepseek-mcp-server/blob/main/CHANGELOG.md
- github.com/arikusi/deepseek-mcp-server/commit/dab07ed93ddde0ab219d4cb7066785847db53a32
- github.com/arikusi/deepseek-mcp-server/pull/4
- github.com/arikusi/deepseek-mcp-server/releases/tag/v1.8.0
- github.com/arikusi/deepseek-mcp-server/security/advisories/GHSA-72f3-6w86-7rv3
- nvd.nist.gov/vuln/detail/CVE-2026-55605
Code Behaviors & Features
Detect and mitigate CVE-2026-55605 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →