Arbitrary API reads via unencoded path IDs
Published Jul 13, 2026 · Updated Jul 13, 2026
Path traversal in zereight mcp-gitlab 2.1.18 allows attackers to read arbitrary GitLab API resources through pipeline and job tools. build/index.js inserts job and pipeline IDs into request paths without segment encoding, so URL normalization collapses crafted ../ sequences. An attacker must control a pipeline or job tool argument; the request stays on the configured GitLab host and uses the operator token.
Summary
What happened
Path traversal in zereight mcp-gitlab 2.1.18 allows attackers to read arbitrary GitLab API resources through pipeline and job tools. build/index.js inserts job and pipeline IDs into request paths without segment encoding, so URL normalization collapses crafted ../ sequences. An attacker must control a pipeline or job tool argument; the request stays on the configured GitLab host and uses the operator token.
The record
- CVE
- CVE-2026-61462
- Published
- Jul 13, 2026
- Updated
- Jul 13, 2026
- Vendor
- zereight
- Product
- mcp-gitlab
- Classifications
- CWE-73, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2026CVE publishedPublication date reported by the CVE source.
- Jul 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.1.18
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- job_id traversal proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo