Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.6

GitLab MCP server can be accessed by malicious web page

CVE-2026-61568 · published 27 days ago
Summary

The GitLab Model Context Protocol server in versions before 2.1.30 lets a crafted web page bypass the usual host checks and reach the local MCP service. An attacker could use this to interact with the server from a victim’s browser. Update to version 2.1.30 or later to close the gap.

What to do
  • Update zereight mcp-gitlab to version 2.1.30.
Affected software
Ecosystem VendorProductAffected versions
– zereight gitlab-mcp < 2.1.30
npm zereight mcp-gitlab < 2.1.30
Fix: upgrade to 2.1.30
Original advisory text
@zereight/mcp-gitlab: DNS rebinding reaches local Streamable HTTP MCP transport
`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Versions prior to 2.1.30 expose the 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. Version 2.1.30 contains a patch.
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
9.6 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-350Reliance on Reverse DNS Resolution for a Security-Critical Action
Timeline
Published15 Sep 2026
Updated11 Oct 2026
First seen15 Sep 2026
Sources
CVE-2026-61568 · NVD
CVE-2026-61568 · MITRE
GHSA-vmp7-252j-cwp7 · GHSA
CVE-2026-61568 · OSV
Track software like this
Free during beta