zereight gitlab-mcp up to 2.1.29 HTTP MCP endpoint dns rebinding

Summaryinfo

A vulnerability classified as critical has been found in zereight gitlab-mcp up to 2.1.29. This vulnerability affects unknown code of the component HTTP MCP endpoint. Performing a manipulation results in dns rebinding. This vulnerability is identified as CVE-2026-61568. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in zereight gitlab-mcp up to 2.1.29. It has been classified as critical. This affects some unknown processing of the component HTTP MCP endpoint. The manipulation with an unknown input leads to a dns rebinding vulnerability. CWE is classifying the issue as CWE-350. The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

`@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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-61568 since 07/10/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1583.002 for this issue.

Upgrading to version 2.1.30 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Bug Tracking Software

Vendor

• zereight

Name

• gitlab-mcp

Version

• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4
• 2.1.5
• 2.1.6
• 2.1.7
• 2.1.8
• 2.1.9
• 2.1.10
• 2.1.11
• 2.1.12
• 2.1.13
• 2.1.14
• 2.1.15
• 2.1.16
• 2.1.17
• 2.1.18
• 2.1.19
• 2.1.20
• 2.1.21
• 2.1.22
• 2.1.23
• 2.1.24
• 2.1.25
• 2.1.26
• 2.1.27
• 2.1.28
• 2.1.29

Website

• Product: https://github.com/zereight/gitlab-mcp/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion