Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61568 critical CVSS 9.6

Vulnerability in @zereight/mcp-gitlab (CVE-2026-61568)

Summary

Vulnerability in @zereight/mcp-gitlab (CVE-2026-61568). Successful exploitation can lead to full system takeover. Exploitable via Authorization header. Mitigation: upgrade to 2.1.30 or later.

Original description

The description as published by the source.

@zereight/mcp-gitlab exposes its Streamable HTTP MCP endpoint without an effective Host or Origin allowlist. A malicious web page can use DNS rebinding to route browser requests to a victim's local MCP listener while preserving an attacker-controlled Host and Origin. The server accepts those headers and reaches the MCP initialization path instead of rejecting the request at the HTTP boundary.

This is CWE-350, Reliance on Reverse DNS Resolution for a Security-Critical Action. The affected package is @zereight/mcp-gitlab version 2.1.18 at commit 74a8c834424ff557ad8bc6f225e4dc5acf80aa13.

The vulnerable transport setup is in index.ts. Express JSON parsing is installed globally before any MCP route-level Host or Origin allowlist:

// index.ts:12077
app.use(express.json());

registerDownloadProxy(app);

The Streamable HTTP transport is then created without the SDK DNS-rebinding controls:

// index.ts:12375
transport = new StreamableHTTPServerTransport({
  sessionIdGenerator: () => randomUUID(),
  onsessioninitialized: (newSessionId: string) => {
    streamableTransports[newSessionId] = transport;
    metrics.totalSessions++;
    metrics.activeSessions++;
  },
});

The transport constructor does not set enableDnsRebindingProtection, allowedHosts, or allowedOrigins. The server also does not add an Express middleware that rejects unexpected Host or Origin headers before /mcp.

The default host is loopback, which is the ex…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61568 has been found in @zereight/mcp-gitlab.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade @zereight/mcp-gitlab to 2.1.30 or later.
If unsure, ask your IT team or search "@zereight/mcp-gitlab CVE-2026-61568" on the vendor's site.

CVE-2026-61568 (@zereight/mcp-gitlab) — CWE-350 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Authorization header / Host / Origin / index.ts
Patched: 2.1.30 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-350) exists in @zereight/mcp-gitlab. Attackers reach the vulnerable code path via Authorization header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @zereight/mcp-gitlab. Attack surface: Authorization header / Host / Origin / index.ts.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.1.30.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@zereight/mcp-gitlab' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@zereight/mcp-gitlab' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @zereight/mcp-gitlab を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @zereight/mcp-gitlab to 2.1.30

    ステージング環境で 2.1.30 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @zereight/mcp-gitlab
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.30"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details