CVE-2026-61462
Path traversal in mcp-gitlab allows API request redirection using operator PAT.
Is CVE-2026-61462 being exploited?
Not confirmed. CVE-2026-61462 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-61462?
CVE-2026-61462 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-61462?
Not known from our data. No patch reference has been recorded for CVE-2026-61462, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-61462 affect?
CVE-2026-61462 affects mcp-gitlab (build/index.js), GitLab API endpoints accessed via operator personal access token, CI/CD pipelines using mcp-gitlab. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-61462?
Implement input validation/filters for job_id, restrict/rotate operator PATs, and apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can craft job_id to redirect GitLab API calls and use the operator's PAT to read/modify repos, pipelines, settings, and exfiltrate data.
Immediate action required
- affected< 2.1.18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.