CVE-2026-61559

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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
Trending — 3 sources updated this weekElevated
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

@zereight/mcp-gitlab is a Model Context Protocol server for GitLab. Starting in version 0.0.1 and prior to version 2.1.27, when the environment variable ENABLE_DYNAMIC_API_URL=true is set, the server reads the X-GitLab-API-URL HTTP request header and uses it as the base URL for all outbound GitLab API calls made within that request. The server validates that the value is a well-formed URL (new URL(dynamicApiUrl)) but applies no allowlist or hostname restriction. The server then attaches the victim's Private-Token to every outbound fetch that uses the redirected URL. Any caller who can reach the HTTP transport can set X-GitLab-API-URL to an attacker-controlled host. The next GitLab API call the server makes delivers the victim's token to that host. Version 2.1.27 contains a patch.

CVSS v3
9.6
EG Score
9.6(medium)
EG Risk
59(Track*)
EG Risk 59/100SSVC: Track*

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 computed
Severity96% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 17, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Server-Side Request Forgery (SSRF) in zereight/mcp-gitlab · Advisory · zereight/gitlab-mcp · GitHub

https://github.com/zereight/gitlab-mcp/security/advisories/GHSA-2h44-8472-frjj
github_release Patch Available

v2.1.27

Patch available: zereight/gitlab-mcp v2.1.27

https://github.com/zereight/gitlab-mcp/releases/tag/v2.1.27
github_pr Patch Available

fix: add remediation hints for GHSA-2h44-8472-frjj dynamic URL rejections

Patch available: zereight/gitlab-mcp v2.1.43 (PR #625 merged 2026-07-26)

https://github.com/zereight/gitlab-mcp/pull/625
github_commit Patch Available

commit 6ffb4cc70706 (zereight/gitlab-mcp)

Patch available: zereight/gitlab-mcp v2.1.43 (contains commit 6ffb4cc70706)

https://github.com/zereight/gitlab-mcp/commit/6ffb4cc70706fd05b1ab80901676bc2998b6db6d

Vendor Advisories for CVE-2026-61559(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)
PackageVulnerable rangeFixed inDependents
@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 9× in last 7d / 9× 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.

  1. 2026-09-18 23:27 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 22:13 UTCEG score recompute
  4. 2026-09-17 18:01 UTCEG score recompute
  5. 2026-09-16 18:19 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-15 21:18 UTCEG score recompute
  8. 2026-09-15 21:03 UTCEG score recompute
  9. 2026-09-15 21:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61559?
CVE-2026-61559 is a critical vulnerability published on September 15, 2026. @zereight/mcp-gitlab is a Model Context Protocol server for GitLab. Starting in version 0.0.1 and prior to version 2.1.27, when the environment variable ENABLEDYNAMICAPI_URL=true is set, the server reads the X-GitLab-API-URL HTTP request header and uses it as the base URL for all outbound GitLab…
When was CVE-2026-61559 disclosed?
CVE-2026-61559 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61559 actively exploited?
CVE-2026-61559 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.4% of all scored CVEs.
What is the CVSS score of CVE-2026-61559?
CVE-2026-61559 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-61559?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61559, 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-61559

Explore →

Is Your Infrastructure Affected by CVE-2026-61559?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs