CVE-2026-44895
CriticalCVSS 9.2Exploitation Probability (EPSS)
Low risk32th percentile - higher than 32% of all known CVEs
Summary
GitLab MCP Server before version 0.6.0 lacks authentication in HTTP transport and uses Access-Control-Allow-Origin: *, allowing anyone to access the RPC endpoint with full access to the GitLab personal access token. The server listens on all network interfaces.
Risk Assessment
An unauthenticated attacker can perform arbitrary operations on GitLab using the operator's token, leading to a complete compromise of repositories and data.
Recommendation
Immediately update GitLab MCP Server to version 0.6.0 or later.
Original NVD description (English source)
GitLab MCP Server lets an AI agent talk directly to GitLab. Prior to 0.6.0, the HTTP transport in src/transport.ts ships with no authentication layer at all and a wildcard Access-Control-Allow-Origin: * on every response. The structural defect is that the SSE server stands up a stateful, mutation-capable RPC endpoint that is backed by the operator's GITLAB_PERSONAL_ACCESS_TOKEN without any inbound credential check, then advertises itself to every cross-origin browser context via the wildcard CORS header. The httpServer.listen(port) call at line 97 also passes no host argument, so the bind defaults to 0.0.0.0 and exposes the auth-less surface on every interface. This vulnerability is fixed in 0.6.0.