Github Mcp Server
Approved changes feed: RSS · Atom
cpe:2.3:a:github:github-mcp-server:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Github (b5027ca2-9bb9-532e-8779-8399b14c3e3b) |
|---|---|
| Product | Github Mcp Server (ef122813-0466-5d71-bc79-8b5be5d91247) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-47427 |
vulnerable | 2026-09-16 04:34:01.101855 |
GitHub MCP Server: Nil Pointer Dereference DoS in completion/complete Handler
HIGH (7.5)
GitHub MCP Server is GitHub's official MCP Server. Prior to 1.1.0, the CompletionsHandler function in pkg/github/server.go accesses params.Ref without first checking whether it is nil, so a completion/complete request with a missing or empty ref field triggers a nil pointer dereference and a Go runtime panic; because the crash occurs before any authentication or token validation, any unauthenticated client able to send JSON-RPC messages can crash the server, resulting in a complete denial of service. This issue is fixed in version 1.1.0.
Published: 2026-07-28T15:32:27.294Z
Updated: 2026-07-28T17:31:19.108Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48529 |
vulnerable | 2026-07-29 00:55:01.390587 |
GitHub MCP Server: Lockdown mode singleton in HTTP server causes cross-user GraphQL client confusion
MEDIUM (6)
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.
Published: 2026-06-26T16:33:32.688Z
Updated: 2026-06-27T02:43:34.588Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.