Homepage

@zereight/mcp-gitlab@2.1.29

GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more

  • latest version

    2.1.42

  • latest non vulnerable version

    2.1.42

  • first published

    1 years ago

  • latest version published

    4 days ago

  • licenses detected

  • View mcp-gitlab package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the @zereight/mcp-gitlab package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Path Traversal

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

    How to fix Path Traversal?

    Upgrade @zereight/mcp-gitlab to version 2.1.38 or higher.

    <2.1.38
    Go back to all versions of this package