GitHub MCP Server: Lockdown mode singleton in HTTP server causes cross-user GraphQL client confusion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| github | github-mcp-server | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Github | Github-mcp-server |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-pjp5-fpmr-3349 | GitHub MCP Server: Lockdown mode singleton in HTTP server causes cross-user GraphQL client confusion |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.166% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Github
Github github-mcp-server |
|
| Vendors & Products |
Github
Github github-mcp-server |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | GitHub MCP Server is GitHub's official MCP Server. From 0.22.0 until 1.1.2, when running in HTTP mode with --lockdown-mode enabled, the RepoAccessCache is implemented as a process-global singleton initialized with the first authenticated user's GraphQL client. All subsequent requests from different users share this singleton and their lockdown-related GraphQL queries are executed using the first user's credentials. The singleton is never updated to reflect later users' tokens. This vulnerability is fixed in 1.1.2. | |
| Title | GitHub MCP Server: Lockdown mode singleton in HTTP server causes cross-user GraphQL client confusion | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV3_1
|