Mcp Gitlab Server
Approved changes feed: RSS · Atom
cpe:2.3:a:yoda-digital:mcp-gitlab-server:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Yoda Digital (dbcb982e-c947-591a-9828-c0378485b409) |
|---|---|
| Product | Mcp Gitlab Server (314bc4bc-488b-5adc-9351-6d622361a426) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-44895 |
vulnerable | 2026-06-08 08:05:11.367816 |
GitLab MCP Server: SSE transport has no authentication and wildcard CORS, exposing all GitLab tools
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.
Published: 2026-05-26T21:08:13.107Z
Updated: 2026-05-27T13:35:15.941Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.