The vulnerability in mcp-gitlab involves external control of the file name or path via the job_id parameter. By supplying crafted values such as ../../../user, an attacker can escape the intended path prefix and redirect API requests to arbitrary GitLab endpoints. This allows unauthorized access to GitLab API resources with the privileges of the operator's personal access token. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges or user interaction required, but with high confidentiality and security scope impact.

Successful exploitation allows attackers to access arbitrary GitLab API resources using the operator's personal access token, potentially exposing sensitive information or enabling unauthorized actions within GitLab. The vulnerability compromises confidentiality and security controls at a high level.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, limit exposure by restricting access to the vulnerable component and monitor for unusual API activity. Avoid using or exposing the vulnerable parameter in untrusted contexts.