CVE-2026-48529: CWE-284: Improper Access Control in github github-mcp-server
A vulnerability in GitHub MCP Server versions prior to 1.1.2 allows improper access control when running in HTTP mode with lockdown mode enabled. The RepoAccessCache singleton is initialized with the first authenticated user's credentials and reused for subsequent users, causing their requests to execute with the first user's permissions. This issue is fixed in version 1.1.2.
AI Analysis
Technical Summary
CVE-2026-48529 describes an improper access control vulnerability (CWE-284) in GitHub MCP Server from versions 0.22.0 up to but not including 1.1.2. When operating 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. Subsequent requests from different users share this singleton, causing their lockdown-related GraphQL queries to execute using the first user's credentials. The singleton is never updated to reflect later users' tokens, leading to potential unauthorized access or privilege escalation within the lockdown context. The vulnerability is resolved in version 1.1.2.
Potential Impact
The vulnerability allows subsequent users' requests to be executed with the credentials of the first authenticated user, potentially leading to unauthorized access or privilege escalation. The CVSS 3.1 base score is 6.0 (medium severity), reflecting network attack vector, high attack complexity, low privileges required, no user interaction, and impacts to confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade GitHub MCP Server to version 1.1.2 or later where this vulnerability is fixed. No other official remediation or temporary fixes are indicated. Since this is not a cloud service, users must apply the patch themselves.
CVE-2026-48529: CWE-284: Improper Access Control in github github-mcp-server
Description
A vulnerability in GitHub MCP Server versions prior to 1.1.2 allows improper access control when running in HTTP mode with lockdown mode enabled. The RepoAccessCache singleton is initialized with the first authenticated user's credentials and reused for subsequent users, causing their requests to execute with the first user's permissions. This issue is fixed in version 1.1.2.
CVSS v3.1
Score 6.0medium
Affected software
pkg:github/github/github-mcp-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48529 describes an improper access control vulnerability (CWE-284) in GitHub MCP Server from versions 0.22.0 up to but not including 1.1.2. When operating 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. Subsequent requests from different users share this singleton, causing their lockdown-related GraphQL queries to execute using the first user's credentials. The singleton is never updated to reflect later users' tokens, leading to potential unauthorized access or privilege escalation within the lockdown context. The vulnerability is resolved in version 1.1.2.
Potential Impact
The vulnerability allows subsequent users' requests to be executed with the credentials of the first authenticated user, potentially leading to unauthorized access or privilege escalation. The CVSS 3.1 base score is 6.0 (medium severity), reflecting network attack vector, high attack complexity, low privileges required, no user interaction, and impacts to confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade GitHub MCP Server to version 1.1.2 or later where this vulnerability is fixed. No other official remediation or temporary fixes are indicated. Since this is not a cloud service, users must apply the patch themselves.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-21T16:18:10.619Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3eae476e08203f7dc7e0c8
Added to database: 06/26/2026, 16:52:23 UTC
Last enriched: 06/26/2026, 17:07:12 UTC
Last updated: 06/26/2026, 17:07:12 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.