# CVE-2026-61462: mcp-gitlab Path Traversal via job_id Parameter

> Attackers can exploit path traversal in the job_id parameter to access arbitrary GitLab API resources using the operator's token.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-5383-j2p9-qfg3

## What is CVE-2026-61462?

CVE-2026-61462 is a critical path traversal vulnerability in zereight mcp-gitlab, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mcp-gitlab contains a path traversal vulnerability in the job_id parameter of build/index.js that allows attackers to redirect GitLab API requests to arbitrary endpoints. Attackers can supply crafted job_id values like ../../../user to escape the intended path prefix and access arbitrary GitLab API resources using the operator's personal access token.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-61462?


## How do I fix CVE-2026-61462?

No fix has been published for CVE-2026-61462 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61462 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61462 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61462 and fix it if it is affected.

What it is: CVE-2026-61462 is a critical path traversal vulnerability in zereight mcp-gitlab, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61462 exists.

Affected product: zereight mcp-gitlab. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61462/ (Markdown: https://insights.sbomify.com/CVE-2026-61462/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61462
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61462
- OSV: https://osv.dev/vulnerability/CVE-2026-61462

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61462/
Summaries are generated and may contain mistakes; the official description above is the record.