Intel

AIKIDO-2026-523251

@zereight/mcp-gitlab is vulnerable to Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF)CVE-2026-61559 Published 4 days ago

96

Critical Risk

This Affects:

JS@zereight/mcp-gitlab
0.0.1 - 2.1.26
Fixed in 2.1.27
Are you affected? Scan for Free

TL;DR

When dynamic API URLs are enabled, the server reads the X-GitLab-API-URL request header and uses it as the base URL for outbound GitLab API calls, validating only that the value is a syntactically valid URL with no host allowlist. The server attaches the caller's Private-Token to those outbound requests, so any caller reaching the HTTP transport can point the header at an attacker-controlled host and receive the victim's GitLab token in a single request. With the stolen token the actor gains full GitLab API access at the victim's permission level, including reading and writing repositories, pipelines, and CI/CD secrets. The fix validates the header host against a configurable allowlist before it is used.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you enable ENABLE_DYNAMIC_API_URL on an HTTP transport.

Background info

@zereight/mcp-gitlab is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.0.1 - 2.1.26.

How to fix this

Upgrade the @zereight/mcp-gitlab library to the patch version.