@zereight/mcp-gitlab
4 published advisories; version 2.1.30 or later fixes all of them.
- Registry
- npm
- Advisories
- 4
- Latest fix
- 2.1.30
- Exploited in the wild
- None listed
Check your machine
Finds @zereight/mcp-gitlab in your agent and MCP configs, installed skills, global npm packages, the npx and uvx caches, uv and pipx tools, Claude Code and Cursor. It runs offline and sends nothing anywhere.
pip install "shieldpi>=0.10.0"
shieldpi agent-config . --installedSource: github.com/zereight/gitlab-mcp, named in a signed build attestation
10 of the last 10 releases of @zereight/mcp-gitlab were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.
- 2.3.29
- 2.3.28
- 2.3.27
- 2.3.26
- 2.3.25
- 2.3.24
- 2.3.23
- 2.3.22
- 2.3.21
- 2.3.20
Green: published with provenance. Grey: without.
OpenSSF Scorecard: 9.5 of 10 on 2026-11-18.
- No dangerous CI workflows
- 10/10
- CI tokens read-only by default
- 10/10
- Build dependencies pinned
- 10/10
- Branch protection
- 8/10
- Changes reviewed before merge
- 10/10
- Signed releases
- 10/10
- Actively maintained
- 10/10
- Security policy
- 10/10
Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.
| Advisory | Severity | Affected | Fixed in | Published |
|---|---|---|---|---|
| @zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeoverCVE-2026-61560 | Critical | < 2.1.27 | 2.1.27 | 2026-09-16 |
| @zereight/mcp-gitlab Vulnerable to Server-Side Request ForgeryCVE-2026-61559 | Critical | >= 0.0.1, < 2.1.27 | 2.1.27 | 2026-09-15 |
| @zereight/mcp-gitlab has multiple safety-control bypasses: execute_graphql read-only + allow-list bypass, unauthenticated transports, sessioGHSA-5648-rgj9-v224 | High | < 2.1.30 | 2.1.30 | 2026-09-15 |
| @zereight/mcp-gitlab: DNS rebinding reaches local Streamable HTTP MCP transportCVE-2026-61568 | Critical | < 2.1.30 | 2.1.30 | 2026-09-15 |
Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].