CyberSecBulletin

Zereight vulnerabilities

We track 4 vulnerabilities in Zereight products across 2 products. 4 are rated high or critical, and none are known to be exploited. The most recent was published on September 15, 2026.

4vulnerabilities
3critical
1high
0exploited
9.4average CVSS score

Latest Zereight vulnerabilities

  • 9.8 Critical severity

    gitlab-mcp: Improper Limitation of a Pathname to a Restricted Directory

    CVE-2026-61560ZereightEPSS 2.9%

    `@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 filesy

  • 9.6 Critical severity

    gitlab-mcp: Reliance on Reverse DNS Resolution for a Security-Critical Action

    CVE-2026-61568Zereight

    `@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Versions prior to 2.1.30 expose the Streamable HTTP MCP endpoint without an effective Host or Origin allowlist. A malicious web page can use DNS rebinding to route browser requests to a vict

  • 9.6 Critical severity

    gitlab-mcp: Server-Side Request Forgery

    CVE-2026-61559Zereight

    `@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 use

  • 8.6 High severity

    mcp-gitlab: External Control of File Name or Path

    CVE-2026-61462Zereight

    mcp-gitlab contains a path traversal vulnerability in the job_id parameter of build/index.js that allows attackers to redirect GitLab API requests to arbitrary endpoints. Attackers can supply crafted job_id values like ../../../user to escape the intended path