Unauthorized MCP access via DNS rebinding
Published Sep 15, 2026 · Updated Sep 15, 2026
DNS rebinding in GitLab MCP Server before 2.1.30 allows remote attackers to reach a victim's local Streamable HTTP MCP endpoint. The HTTP boundary accepts attacker-controlled Host and Origin headers instead of restricting them to trusted values, allowing rebound requests to enter MCP initialization. Exploitation requires a victim to visit a malicious page while the listener is running, exposing MCP operations under the server's configured GitLab credentials.
Summary
What happened
DNS rebinding in GitLab MCP Server before 2.1.30 allows remote attackers to reach a victim's local Streamable HTTP MCP endpoint. The HTTP boundary accepts attacker-controlled Host and Origin headers instead of restricting them to trusted values, allowing rebound requests to enter MCP initialization. Exploitation requires a victim to visit a malicious page while the listener is running, exposing MCP operations under the server's configured GitLab credentials.
The record
- CVE
- CVE-2026-61568
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- zereight
- Product
- GitLab MCP Server
- Classifications
- T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.30
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo