dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-44895

CRITICAL · 9.2 CVSS v4.0 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab MCP Server versions before 0.6.0 have an unauthenticated HTTP transport that exposes a stateful, mutation-capable RPC endpoint backed by the operator's GITLAB_PERSONAL_ACCESS_TOKEN. The server binds to all interfaces (0.0.0.0) with wildcard CORS, allowing any cross-origin browser context to make authenticated API calls to the user's GitLab instance.

MitigationUpgrade to GitLab MCP Server 0.6.0 or later which adds proper authentication and restricts CORS; if unable to upgrade, disable the HTTP transport or bind only to localhost.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitLab MCP Server installation
    Locate the GitLab MCP Server in your environment and determine its running process or installed package
    Affected if GitLab MCP Server is installed and running with HTTP transport enabled
  2. Determine installed version
    Check the version of the GitLab MCP Server (e.g., via --version flag, package manager, or process metadata)
    Affected if The version is prior to 0.6.0 (any version from initial release up to but not including 0.6.0)
  3. Verify network binding configuration
    Inspect the server's network configuration or running parameters to determine which interface it binds to
    Affected if The SSE HTTP server is bound to 0.0.0.0 (all interfaces) rather than localhost only
  4. Inspect CORS headers
    Send an HTTP request to the MCP Server endpoint and examine the Access-Control-Allow-Origin response header
    Affected if The header is set to '*' (wildcard) allowing any cross-origin access
  5. Confirm authentication status
    Review the server configuration or documentation to verify if inbound authentication is required
    Affected if No authentication layer is required to access the RPC endpoint

You are affected if GitLab MCP Server versions prior to 0.6.0 are running with HTTP transport bound to all interfaces and lacking inbound authentication and CORS restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to GitLab MCP Server 0.6.0 or later which adds proper authentication and restricts CORS; if unable to upgrade, disable the HTTP transport or bind only to localhost.

Recommended fix High confidence

0.6.0 or later

  1. Identify the currently installed GitLab MCP Server version using npm list @anthropic-ai/gitlab-mcp-server or your package manager
  2. Stop any running GitLab MCP Server instances
  3. Upgrade to version 0.6.0 or later by running: npm update @anthropic-ai/gitlab-mcp-server@latest or npm install @anthropic-ai/[email protected]
  4. Verify the installed version matches or exceeds 0.6.0
  5. Restart the GitLab MCP Server with the updated version
  6. Confirm the service is running correctly and accessible only on intended network interfaces if you were previously exposed
Caveat Review changelog for any configuration or behavioral changes between your current version and 0.6.0, though the description indicates this is a security-focused patch

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44895 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data