mcp-gitlab Path Traversal via job_id Parameter

Answer in brief

CVE-2026-61462 records a Critical severity (CVSS 9.2) vulnerability in mcp-gitlab Path Traversal via job_id Parameter. The current sources do not mark it as known exploited. The current feed maps zereight/mcp-gitlab (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 13, 2026Updated Sep 24, 2026Source checked Sep 24, 2026First seen by HOL Jul 13, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.2
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 9.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps zereight/mcp-gitlab (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
zereight/mcp-gitlabgeneric	*	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for zereight/mcp-gitlab.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Jul 13, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 13, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.