@zereight/mcp-gitlab is a Model Context Protocol server for GitLab. Prior to version 2.1.27, the SSE transport mode (SSE=true) exposes all MCP tools without any authentication. The upload_markdown tool reads arbitrary files from the server's local filesystem via an unsanitized file_path parameter and uploads them to a GitLab project. Combined, any unauthenticated network-reachable attacker can read /proc/self/environ to steal the server's GITLAB_PERSONAL_ACCESS_TOKEN and achieve full GitLab account takeover. This is the default configuration for Docker deployments. Version 2.1.27 contains a patch.
CVE-2026-61560
CRITICALPre-NVD 9.89.8—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 48% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 52%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 16, 2026🔬 Proof of concept available. Patch available. Sources: github_pr, github.
github Patch Available🟡 PoC Available
Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover · Advisory · zereight/gitlab-mcp · GitHub
https://github.com/zereight/gitlab-mcp/security/advisories/GHSA-cv3r-c5h8-f4g5github_pr Patch Available
docs: document GHSA-cv3r-c5h8-f4g5 security fix
Patch available: zereight/gitlab-mcp v2.1.43 (PR #622 merged 2026-07-26)
https://github.com/zereight/gitlab-mcp/pull/622github_pr Patch Available
fix: guard exposed SSE transport
Patch available: zereight/gitlab-mcp v2.1.32 (PR #554 merged 2026-06-22)
https://github.com/zereight/gitlab-mcp/pull/554github_pr Patch Available
fix: make download and upload work for remote deployments
Patch available: zereight/gitlab-mcp v2.1.32 (PR #482 merged 2026-05-21)
https://github.com/zereight/gitlab-mcp/pull/482Vendor Advisories for CVE-2026-61560(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @zereight/mcp-gitlab | — | 2.1.27 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 22:11 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 22:20 UTCEG score recompute
- 2026-09-16 18:21 UTCEG score recompute
- 2026-09-16 14:24 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 14:06 UTCEG score recompute
- 2026-09-15 22:20 UTCEG score recompute
- 2026-09-15 21:18 UTCEG score recompute
- 2026-09-15 21:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-61560?
CVE-2026-61560 is a critical vulnerability published on September 15, 2026. @zereight/mcp-gitlab is a Model Context Protocol server for GitLab. Prior to version 2.1.27, the SSE transport mode (SSE=true) exposes all MCP tools without any authentication. The uploadmarkdown tool reads arbitrary files from the server's local filesystem via an unsanitized filepath parameter and…
When was CVE-2026-61560 disclosed?
CVE-2026-61560 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61560 actively exploited?
CVE-2026-61560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.2% of all scored CVEs.
What is the CVSS score of CVE-2026-61560?
CVE-2026-61560 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-61560?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61560, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61560
Is Your Infrastructure Affected by CVE-2026-61560?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.