High, CVSS 8.8npmAmendedPublished
@yoda.digital/gitlab-mcp-server's SSE transport has no authentication and wildcard CORS, exposing all 86 GitLab tools
CVE-2026-44895 · GHSA-8jr5-6gvj-rfpf
- Affected
- npm @yoda.digital/gitlab-mcp-server < 0.6.0
- Fixed in
- 0.6.0· Vendor fix available
- Issue
- SSE Transport Has No Authentication and Wildcard CORS, Exposing All 86 GitLab Tools Including Destructive Operations A review of mcp-gitlab-server at commit 80a7b4cf3fba6b55389c0ef491a48190f7c8996a uncovered that the SSE HTTP transport — advertised in the README and comparison table as a differentiating feature — runs with no authentication and wildcard CORS on every endpoint. The maintainers' own roadmap confirms auth is a known gap. When USESSE=true, the HTTP server in src/transport.ts sets: The httpServer.listen(port) call at line 97 passes no host argument — Node.js defaults to 0.0.0.0, binding on all interfaces. Two endpoints are exposed with no credential check: - GET /sse — opens an SSE connection, returns a session endpoint URL - POST /messages?sessionId=<id — sends MCP messages to the server using the loaded GITLABPERSONALACCESSTOKEN Any caller who can reach the port — LAN, cloud instance, or via the browser-tab vector the wildcard CORS enables — gets full access to all 86…
Recommended action: Upgrade to 0.6.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.