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

> Unauthenticated access to the GitLab MCP Server allows attackers to execute GitLab operations using the operator's token due to missing authentication and wildcard CORS.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-8jr5-6gvj-rfpf

## What is CVE-2026-44895?

CVE-2026-44895 is a critical missing authorization vulnerability in yoda-digital mcp-gitlab-server, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-44895?

2 open source packages ship an affected version, including @yoda.digital/gitlab-mcp-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@yoda.digital/gitlab-mcp-server` | npm | All versions | 0.6.0 |
| `@yoda.digital/gitlab-mcp-server` | npm | All versions | 0.6.0 |

## How do I fix CVE-2026-44895?

Upgrade @yoda.digital/gitlab-mcp-server to 0.6.0 or later.

## Is CVE-2026-44895 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44895 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44895 and fix it if it is affected.

What it is: CVE-2026-44895 is a critical missing authorization vulnerability in yoda-digital mcp-gitlab-server, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44895 exists.

Affected packages and fixed versions:
- @yoda.digital/gitlab-mcp-server (npm): affected all versions; fixed in 0.6.0
- @yoda.digital/gitlab-mcp-server (npm): affected all versions; fixed in 0.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44895/ (Markdown: https://insights.sbomify.com/CVE-2026-44895/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44895
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44895
- OSV: https://osv.dev/vulnerability/CVE-2026-44895

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44895/
Summaries are generated and may contain mistakes; the official description above is the record.