@zereight/mcp-gitlab: DNS rebinding reaches local Streamable HTTP MCP transport
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.30
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The @zereight/mcp-gitlab package, a Model Context Protocol server for GitLab, is affected when its Streamable HTTP endpoint is run locally. A malicious website could use DNS rebinding to send requests from a victim's browser to that local server, allowing an attacker to reach the MCP initialization process and potentially act through the server's GitLab access.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
`@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.
Timeline
- CVE published
- Record last updated
Affected versions
- zereight gitlab-mcp
fixed in 2.1.30
- @zereight/mcp-gitlabnpm
fixed in 2.1.30