Which products and versions are affected by CVE-2026-61560?

Affected: @zereight/mcp-gitlab (npm); gitlab-mcp. The full list is in the CVE brief.

Is CVE-2026-61560 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2026-61560 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2026-61560?

Public exploit code is available.

Is there a fix for CVE-2026-61560?

Fixed versions are available, including @zereight/mcp-gitlab 2.1.27, gitlab-mcp 2.1.27.

How urgently should CVE-2026-61560 be patched?

Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Request A Demo

Vulnerability Intelligence

CVE-2026-61560

CriticalPublic exploit

Prior to version 2.1.27, the SSE transport mode (SSE=true) exposes all MCP tools without any authentication.

Published Sep 15, 2026 · Updated Oct 2, 2026 · Also known as EUVD-2026-80008, GHSA-cv3r-c5h8-f4g5

Key Facts

Patch immediately

CVE-2026-61560 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting @zereight/mcp-gitlab (npm), gitlab-mcp.
It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
EPSS estimates a 2.9% probability of exploitation in the next 30 days.
Fixed versions are available, including @zereight/mcp-gitlab 2.1.27, gitlab-mcp 2.1.27.
Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

CVSS v3.1

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

2.9%

Higher than 86.7% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2026-61560 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

@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.

Affected Products

2 affected entries in total

Product	Affected versions	Fixed in
@zereight/mcp-gitlabnpm	See advisory	2.1.27
gitlab-mcp	See advisory	2.1.27

Patched Releases

@zereight/mcp-gitlab

2.1.27

gitlab-mcp

2.1.27

Timeline

Publicly disclosed
Sep 15, 2026
Last updated
Oct 2, 2026

Weakness Type

CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

References

5 more references in the full CVE brief

FAQ

Common Questions.

@zereight/mcp-gitlab is a Model Context Protocol server for GitLab.
Affected: @zereight/mcp-gitlab (npm); gitlab-mcp. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including @zereight/mcp-gitlab 2.1.27, gitlab-mcp 2.1.27.
Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Is CVE-2026-61560 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.