Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.6amended

@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery

CVE-2026-61559GHSA-2h44-8472-frjj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@zereight/mcp-gitlab 2.1.27), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-61559: 0.43% estimated exploitation activity in the next 30 days; percentile 36.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Server-Side Request Forgery via X-GitLab-API-URL Header Allows Credential Theft Affected - Repository: zereight/gitlab-mcp - Affected versions: All versions through commit 74a8c83 - Patched versions: None at time of report Severity High. CVSS v3.1 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N) Description When the environment variable ENABLEDYNAMICAPIURL=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. The vulnerable code appears at two locations. SSE handler…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-2h44-8472-frjj

  2. Revision 2 · amended ·

    Amended from osv record GHSA-2h44-8472-frjj

  3. Revision 1 · created ·

    Published from ghsa record GHSA-2h44-8472-frjj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61559

Advisory: @zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery
IDs: CVE-2026-61559, GHSA-2h44-8472-frjj
Record: https://patchnext.com/advisories/cve-2026-61559 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @zereight/mcp-gitlab 2.1.27. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @zereight/mcp-gitlab: affected >= 0.0.1, < 2.1.27; fixed in 2.1.27

## Suggested inspection (read-only)
- `npm ls @zereight/mcp-gitlab --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @zereight/mcp-gitlab.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2h44-8472-frjj (GitHub-reviewed advisory GHSA-2h44-8472-frjj lists affected ranges: npm @zereight/mcp-gitlab >=0.0.1 <2.1.27)
- Verified: https://osv.dev/vulnerability/GHSA-2h44-8472-frjj (OSV record GHSA-2h44-8472-frjj lists affected ranges: npm @zereight/mcp-gitlab >=0.0.1 <2.1.27 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…