CVE-2026-44895

Critical

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.

SeverityCritical
CVSS9.2
Exploit probability—
Product@yoda.digital/gitlab-mcp-server
PublishedMay 26, 2026
First seenMay 26, 2026

How to fix

Update
  • @yoda.digital/gitlab-mcp-server0.6.0 or later

Affected products

ProductAffected versionsFixed in
@yoda.digital/gitlab-mcp-servernpmv < 0.6.00.6.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.