Skip to content

CVE-2026-44895 GitLab MCP Server: SSE transport has no authentication and wildcard CORS, exposing all GitLab tools

CriticalCVSS 9.2 EPSS 0.45%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: yes · technical impact: total

Description

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.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
yoda.digital @yoda.digital/gitlab-mcp-server(npm) < 0.6.0 0.6.0 Fixed
yoda-digital mcp-gitlab-server = < 0.6.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
yoda-digital mcp-gitlab-server = < 0.6.0 No fix listed
yoda.digital @yoda.digital/gitlab-mcp-server(npm) < 0.6.0 0.6.0

References