GitHub MCP Server: Lockdown mode singleton in HTTP server causes cross-user GraphQL client confusion
CVE-2026-48529 · GHSA-pjp5-fpmr-3349 · published 2026-06-25
- Severity
- Medium
- CVSS score
- 6.0
- Chance of exploitation (EPSS)
- 0.17%
- Fixed in
- 1.1.2
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
This affects deployments running the HTTP server with --lockdown-mode, which is the intended configuration for multi-user scenarios such as GitHub Copilot's managed MCP endpoint. Three concrete consequences: First, the ViewerLogin field in cache entries always reflects the first authenticated user's identity. The IsSafeContent check compares this stale value against each subsequent user's login, producing incorrect results for all users except the first. Second, repository visibility and collaborator access data stored in the cache is evaluated through the first user's token.
Upgrade github.com/github/github-mcp-server to 1.1.2 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| github.com/github/github-mcp-server | Go | >= 0.22.0, < 1.1.2 | 1.1.2 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- HighGitHub MCP Server has Nil Pointer Dereference DoS in completion/complete Handlergithub.com/github/github-mcp-server
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.