CVE-2026-47427: GitHub MCP Server has Nil Pointer Dereference DoS in completion/complete Handler
The GitHub MCP Server (Go module github.com/github/github-mcp-server) crashes when it gets a completion/complete request with missing or empty parameters. Any client that can send JSON-RPC messages to the server can kill the process. Versions below 1.1.0 are affected; 1.1.0 fixes it.
Published Jul 28, 2026 · Analysis Nov 1, 2026
What an attacker can do
CompletionsHandler in pkg/github/server.go reads params.Ref without checking whether it is nil. A completion/complete request with empty params, or with an argument but no ref field, makes the Go runtime panic with a nil pointer dereference. The panic is not recovered and ends the process.
The advisory says the crash happens before authentication or token validation, so even a request carrying a fake token triggers it. The attacker only needs to complete the MCP initialization handshake and reach the server's transport. A server wired to a local editor over stdio is reachable only by that client. A server exposed over HTTP to other users or the network can be knocked offline by anyone who can reach it.
The effect is denial of service only. There is no data exposure or code execution, matching the availability-only CVSS vector. Any agent that depends on the server loses its GitHub tools until someone restarts it. The reporter's fuzzing with mcpsec found 108 crashes in 925 test cases.
Who is affected
github.com/github/github-mcp-server below 1.1.0. The reporter re-verified the crash on v0.33.0. Check which version you run:
github-mcp-server --versionFor a source or module build, check go.mod:
go list -m github.com/github/github-mcp-serverContainer users should check the image tag. Instances reachable over HTTP by untrusted clients carry the most risk.
github.com/github/github-mcp-server
- Ecosystem
- Go
- Affected
- < 1.1.0
- Fixed in
- 1.1.0
- Check
go list -m github.com/github/github-mcp-server
How to fix it
Upgrade to github-mcp-server 1.1.0. The fix, in pull request 2502, adds a nil guard to CompletionsHandler. It checks req, req.Params and req.Params.Ref, and returns an error for a malformed request instead of dispatching on Ref.Type. A test, TestCompletionsHandler_RejectsMissingRef, covers the three nil cases.
go get github.com/github/[email protected]The sources give no workaround. Until you upgrade, keep the server reachable only by trusted local clients and restart it automatically on exit.
How to tell if you were hit
Look for process exits and this panic in server logs or container output:
panic: runtime error: invalid memory address or nil pointer dereferenceThe stack trace names github.com/github/github-mcp-server/pkg/github.NewMCPServer.CompletionsHandler.func1 at pkg/github/server.go:198. Repeated restarts of the process, or a client that sends completion/complete right after initialize, point to exploitation. Beam records agent MCP tool calls and can show when GitHub tools stop responding, but it does not see the server crash itself.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
A nil pointer dereference vulnerability in the GitHub MCP Server causes it to crash when receiving a malformed completion/complete request with missing or empty parameters. This allows any unauthenticated client to cause a complete denial of service.
Details
The CompletionsHandler function in pkg/github/server.go:198 accesses params.Ref without checking if it's nil first. When a client sends a completion/complete request with a missing ref field, the handler dereferences nil and the Go runtime panics.
The crash occurs before any authentication or token validation, so even requests with fake tokens can trigger it.
PoC
After completing the MCP initialization handshake, send either:
Empty params:
{"jsonrpc":"2.0","id":2,"method":"completion/complete","params":{}}
Missing ref field:
{"jsonrpc":"2.0","id":2,"method":"completion/complete","params":{"argument":{"name":"x","value":"y"}}}
Result:
panic: runtime error: invalid memory address or nil pointer dereference goroutine 42 [running]: github.com/github/github-mcp-server/pkg/github.NewMCPServer.CompletionsHandler.func1(...) pkg/github/server.go:198 +0x24
Impact
Any unauthenticated client that can send JSON-RPC messages to the server can crash it immediately. This is a complete denial of service - the panic is unrecoverable and kills the process.
Automated fuzzing with mcpsec found 108 crashes out of 925 test cases (11.7% crash rate).
Timeline
- Feb 21, 2026 - Initial report sent to [email protected]
- Mar 03, 2026 - Follow-up email sent, no response
- Mar 21, 2026 - Re-verified on v0.33.0, sent detailed report with PoC, no response
- Apr 06, 2026 - GHSA filed after 44 days without acknowledgment
Suggested Fix
func (s *Server) CompletionsHandler(ctx context.Context, params *mcp.CompleteParams) (*mcp.CompleteResult, error) { if params == nil || params.Ref == nil { return nil, fmt.Errorf("invalid request: missing ref parameter") } // ... rest of handler }
Credited to manthanghasadiya.
Questions
- Does CVE-2026-47427 need a GitHub token?
No. The crash occurs before authentication or token validation, so a request with a fake token also triggers it. The client does have to complete the MCP initialization handshake first.
- Can this lead to code execution or data theft?
No source says so. The flaw is a nil pointer dereference that panics the Go process. The impact is denial of service.
- Which version fixes the crash?
1.1.0. All versions below it are listed as vulnerable, and the reporter confirmed the bug on v0.33.0.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Other MCP servers and tools vulnerabilities
All Other MCP servers and tools entriesCVE-2026-129235
Kubeshark: MCP `download_file` writes fetched bytes to an unvalidated destination path
medium5.3Nov 16, 2026CVE-2026-129236
Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → image redirect → cluster takeover
high7.2Nov 16, 2026CVE-2026-68934
code-review-mcp-server: Command injection via unsanitized folderPath/baseBranch parameters
high8.7Nov 16, 2026CVE-2026-102943
Dagu MCP DAG specification read bypasses path containment and workspace isolation
medium6.5Nov 10, 2026CVE-2026-102610
fast-agent: `fast-agent serve` binds HTTP to 0.0.0.0 with no authentication by default; with --shell this is unauthenticated remote command execution
medium6.4Nov 9, 2026CVE-2026-63655
tsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS
high7.5Nov 9, 2026
