Quick answers
- Is CVE-2026-61462 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61462 being exploited in the wild.
- How severe is CVE-2026-61462?
- High severity, with a CVSS score of 8.6, published 13 July 2026.
- Which products and versions are affected?
- Zereight Mcp-Gitlab < 2.1.18.
- Is there a fix for CVE-2026-61462?
- A patch was published on 2026-07-10: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61462 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-61462?
- Check whether you run Zereight Mcp-Gitlab at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in mcp-gitlab (specifically within build/index.js) due to improper sanitization of the 'job_id' and 'pipeline_id' parameters. While 'project_id' is URL-encoded, 'job_id' is interpolated raw into GitLab API request URLs. Because the 'new URL()' constructor in Node.js normalizes path segments, an attacker can provide a crafted value such as '../../../user' to escape the intended '/projects/{id}/jobs/' path prefix. This allows the attacker to reach arbitrary GitLab API v4 endpoints. Since these requests are authenticated using the operator's GITLAB_PERSONAL_ACCESS_TOKEN, the exploit can lead to unauthorized data disclosure from the GitLab instance. The issue is fixed in version 2.1.18 by ensuring path segments are properly encoded.
Affected products
- zereight mcp-gitlab (npm package) < 2.1.18
Timeline
- 2026-06-05: other: Initial report to vendor
- 2026-07-10: patched: Fix committed to repository
- 2026-07-13: disclosed: CVE published