Hosted `check_dependency_vulnerabilities` silently omits medium-severity advisories
Mantenedores costumam responder em até 2 dias
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 30/100
Direção de pesquisa
The implicated tool check_dependency_vulnerabilities does not exist in this repository's source or history — it is hosted-only at https://api.githubcopilot.com/mcp/, so the fix cannot be made from this repo. Start by reading pkg/github/security_advisories.go (lines ~53-57 and ~150-188) to confirm the public wrapper forwards severity only when supplied, then reproduce the mismatch with the gh api /advisories commands in the issue. Done means either locating the internal repository where the hosted wrapper lives or filing a documented minimal reproduction for the maintainers; a newcomer here can only verify and triage, not patch.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Describe the bug
The hosted GitHub MCP Server tool check_dependency_vulnerabilities appears to return only high-severity advisories while silently omitting applicable medium-severity advisories.
This can produce a misleading result such as 0 vulnerable or No known vulnerabilities found for package versions that the GitHub Advisory Database identifies as vulnerable. Consumers using the tool to verify dependency safety can therefore receive an incomplete result without any indication that a severity filter was applied.
The tool is available through the hosted endpoint at https://api.githubcopilot.com/mcp/. It does not appear in the public source or Git history of this repository. The repository's remote-server documentation notes that the hosted server binds this repository into GitHub infrastructure through an internal repository and may provide additional hosted-only tools.
Affected version
Hosted remote GitHub MCP Server at https://api.githubcopilot.com/mcp/, reproduced on October 6, 2026.
The hosted service does not expose a server version through this tool. This is not reproducible through the published local Docker image because check_dependency_vulnerabilities is a hosted-only tool.
Steps to reproduce the behavior
-
Connect to the hosted GitHub MCP Server at
https://api.githubcopilot.com/mcp/with access to thecheck_dependency_vulnerabilitiestool. -
Invoke the tool with this public repository and these dependencies:
{ "owner": "github", "repo": "github-mcp-server", "dependencies": [ { "ecosystem": "npm", "name": "yargs-parser", "version": "9.0.2" }, { "ecosystem": "npm", "name": "uuid", "version": "8.0.0" }, { "ecosystem": "npm", "name": "lodash", "version": "4.17.20" } ] } -
Observe that only the two high-severity lodash advisories are returned. No vulnerability is reported for
[email protected]or[email protected]. -
Query the GitHub Advisory Database with the same affected package versions:
gh api --method GET /advisories \ -f ecosystem=npm \ -f '[email protected]' \ --jq '.[] | select(.withdrawn_at == null) | {ghsa_id,severity}' gh api --method GET /advisories \ -f ecosystem=npm \ -f '[email protected]' \ --jq '.[] | select(.withdrawn_at == null) | {ghsa_id,severity}' -
Observe the applicable non-withdrawn medium-severity advisories:
{"ghsa_id":"GHSA-p9pc-299p-vxgp","severity":"medium"} {"ghsa_id":"GHSA-w5hq-g745-h8pq","severity":"medium"}
As a control, querying [email protected] directly returns two high and three non-withdrawn medium advisories. The checker returns exactly the two high advisories and omits all three medium advisories.
Expected vs actual behavior
Expected:
check_dependency_vulnerabilities should return every applicable advisory, or accept and clearly document an explicit severity threshold. If results are intentionally filtered, the response should identify the effective threshold and must not state No known vulnerabilities found without qualification.
For this request, the result should include at least:
[email protected]:GHSA-p9pc-299p-vxgp(medium), vulnerable range>= 6.0.0, < 13.1.2[email protected]:GHSA-w5hq-g745-h8pq(medium), vulnerable range< 11.1.1- The applicable high and medium advisories for
[email protected]
Actual:
The checker reports only the two high-severity lodash advisories and treats the two medium-severity dependencies as not vulnerable. The response gives no indication that medium and lower severities were excluded.
Logs
Actual hosted-tool output from the reproduction:
Dependency Vulnerability Report for github/github-mcp-server
Checked 3 dependency(ies). 1 vulnerable.
⚠ [email protected] (npm) — 2 vulnerability(ies) found
- GHSA-r5fr-rjxr-66jc [high]: lodash vulnerable to Code Injection via `_.template` imports key names
→ Upgrade to 4.18.0 to mitigate
- GHSA-35jh-r3h4-6jhm [high]: Command Injection in lodash
→ Upgrade to 4.17.21 to mitigate
Found 2 total vulnerability(ies) across 1 dependency(ies)
The public list_global_security_advisories tool on the same hosted MCP server returns the omitted medium advisories when called without a severity filter. In the public implementation, the severity argument is optional and is only forwarded when explicitly provided:
- https://github.com/github/github-mcp-server/blob/bf0f67fa572e2926c30506fe89c859b360c1d110/pkg/github/security_advisories.go#L53-L57
- https://github.com/github/github-mcp-server/blob/bf0f67fa572e2926c30506fe89c859b360c1d110/pkg/github/security_advisories.go#L150-L188
This evidence suggests the filtering occurs in the hosted-only check_dependency_vulnerabilities wrapper or its post-query processing rather than in the public advisory API wrapper.
- Linguagem predominante
- Go
- Estrelas
- 34.4k
- Forks
- 5.3k
- Merge médio
- 3d 10h
- PRs com merge (30d)
- 11
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de github/github-mcp-server
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
github/github-mcp-server#3865 ·
Mantenedores costumam responder em até 2 dias
-
update_issue_labels is annotated destructiveHint: false but replaces (removes) existing labelsTalvez já em andamento @shhhhhhjokerist assumiu há 6 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 69/100
github/github-mcp-server#3760 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
docs(install-claude): "environment variable" examples put the PAT in argv and the saved configTalvez já em andamento @shhhhhhjokerist assumiu há 6 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
github/github-mcp-server#3758 ·
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 69/100
github/github-mcp-server#3729 ·
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
github/github-mcp-server#3722 ·
Mantenedores costumam responder em até 2 dias
Todas as issues de github/github-mcp-server
Issues semelhantes
-
kind/features
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
TencentBlueKing/bk-nodemgr#4017 ·
Mantenedores costumam responder em até 1 dia
-
ssa: wait errors drop the kstatus message, so health check failures don't say whyTalvez já em andamento @schdief assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
equinor/radix-operator#2066 ·
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
microsoft/terraform-provider-msgraph#188 · 1 reação ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
Mantenedores costumam responder em até 2 dias