Path Traversal Affecting @zereight/mcp-gitlab package, versions <2.1.38
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-ZEREIGHTMCPGITLAB-18020327
- published20 Jul 2026
- disclosed13 Jul 2026
- creditGeorge Chen
Introduced: 13 Jul 2026
NewCVE-2026-61462 (opens in a new tab)How to fix?
Upgrade @zereight/mcp-gitlab to version 2.1.38 or higher.
Overview
@zereight/mcp-gitlab is a GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more
Affected versions of this package are vulnerable to Path Traversal in the job URL construction in build/index.js, which interpolates the job_id parameter into GitLab API URLs unencoded, while project_id is URL-encoded, so that .. segments are normalized by new URL() and escape the intended /projects/{id}/jobs/{job_id}/ path. An attacker who can influence the job_id argument, through prompt injection or other LLM manipulation, can redirect a scoped job tool to arbitrary /api/v4/ endpoints under the operator's personal access token and read account data, projects, and resources beyond the job scope, by supplying a job_id containing traversal segments. Exploitation requires a configured GITLAB_PERSONAL_ACCESS_TOKEN, and the request host stays fixed to the operator-configured GITLAB_API_URL, so access is confined to that GitLab instance.