cve.bz

CVE-2026-61568 zereight gitlab-mcp

9.6 criticalEPSS 0.5%Fix available

Critical (9.6) in zereight gitlab-mcp. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in @zereight/mcp-gitlab 2.1.30.

On this page
`@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 victim's local MCP listener while preserving an attacker-controlled `Host` and `Origin`. The server accepts those headers and reaches the MCP initialization path instead of rejecting the request at the HTTP boundary. Version 2.1.30 contains a patch.

Severity

CVSS 3.1

9.6 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-350 Reliance on Reverse DNS Resolution for a Security-Critical Action
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @zereight/mcp-gitlab (npm): fixed in 2.1.30

Ask an AI about this CVE

Show the promptExplain CVE-2026-61568 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61568?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61568?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61568 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
zereight gitlab-mcp< 2.1.30

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vmp7-252j-cwp7npm@zereight/mcp-gitlab<2.1.302.1.30

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-89 Pharming Likelihood: High · Severity: Very High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-275 DNS Rebinding Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON