CVE-2026-61559
CRITICALDescription
`@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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 19% of all known CVEs.
References
Related Vulnerabilities
Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-21893 | High | 8.2 | 100% | KEV + Ransom | - |
| CVE-2021-40438 | Critical | 9.0 | 100% | KEV + Ransom | Fix |
| CVE-2021-34473 | Critical | 9.1 | 100% | KEV + Ransom | Fix |
| CVE-2021-21985 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2021-26855 | Critical | 9.1 | 100% | KEV + Ransom | Fix |
| CVE-2022-41040 | High | 8.8 | 100% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-61559?
Upgrade @zereight/mcp-gitlab to 2.1.27 or later.
Is CVE-2026-61559 being actively exploited?
Not that we know of. CVE-2026-61559 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.27% is the estimated probability that it will be exploited in the next 30 days. That is higher than 19% of all scored CVEs.
How severe is CVE-2026-61559?
CVE-2026-61559 has a CVSS v3 base score of 9.6, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-61559 affect?
Published advisories record a fix for @zereight/mcp-gitlab (npm). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-61559
Markdown
[](https://tridentstack.com/cve/CVE-2026-61559)HTML
<a href="https://tridentstack.com/cve/CVE-2026-61559"><img src="https://tridentstack.com/cve/badge/CVE-2026-61559.svg" alt="CVE-2026-61559"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-17.