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 misuse leverages the operator's personal access token, potentially exposing sensitive API resources. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges or user interaction required, but with high impact on confidentiality and security capabilities. No vendor advisory or patch information is available at this time.

Successful exploitation allows an unauthenticated attacker to access arbitrary GitLab API resources with the privileges of the operator's personal access token. This can lead to unauthorized disclosure of sensitive information and potential compromise of GitLab data accessible via the API. The vulnerability affects confidentiality and security capabilities with a critical severity rating.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the vulnerable mcp-gitlab component and monitor for suspicious usage of the job_id parameter. Avoid exposing the operator's personal access token in contexts where this vulnerability could be exploited.