CVE-2026-61568 @zereight/mcp-gitlab: DNS rebinding reaches local Streamable HTTP MCP transport
Attackers can use DNS rebinding to bypass host checks and access local GitLab MCP endpoints, potentially reading data or bypassing security controls.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-61568?
CVE-2026-61568 is a critical server-side request forgery vulnerability in zereight gitlab-mcp, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
`@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.
Weakness: CWE-350
Which versions are affected by CVE-2026-61568?
2 open source packages ship an affected version, including @zereight/mcp-gitlab.
| Package | Affected | Fixed in |
|---|---|---|
@zereight/mcp-gitlab npm | All versions | 2.1.30 |
@zereight/mcp-gitlab npm | All versions | 2.1.30 |
How do I fix CVE-2026-61568?
Upgrade @zereight/mcp-gitlab to 2.1.30 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-61568 being exploited?
There is no known exploitation of CVE-2026-61568 in the wild and no public exploit code.
Sources
Also known as GHSA-vmp7-252j-cwp7.