Repository advisory GHSA-7v25-vcp6-4hcr not in global Advisory Database
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
This is a request for the GitHub Advisory Database curation team to review a published repository advisory for inclusion. The issue is about process and database synchronization, not code changes. A newcomer would need to understand the advisory database ingestion pipeline, the criteria for inclusion, and how to escalate a stuck advisory. Check the repository's contribution guidelines and existing similar issues to see how curation requests are handled. 'Done' means the advisory appears in the global database.
Written by the indexing model from the issue text.
Description
Summary
I maintain tumf/mcp-shell-server. Repository advisory GHSA-7v25-vcp6-4hcr was published on 2026-09-19 and remains absent from the global GitHub Advisory Database more than 72 hours later.
Advisory
- Repository advisory: https://github.com/tumf/mcp-shell-server/security/advisories/GHSA-7v25-vcp6-4hcr
- Package:
mcp-shell-server(pip) - Affected versions:
<= 1.1.11 - Patched version:
1.1.12 - CWE: CWE-88
- Severity: High
- Reporter credit: accepted
The advisory describes Git global options with separated values causing the validator to misidentify the subcommand, allowing persistent git config writes and later command execution when git is allowlisted. Version 1.1.12 fixes the affected parser state.
Current state
- Repository advisory state:
published cve_id:nullsubmission.accepted:falseGET /advisories/GHSA-7v25-vcp6-4hcr:404 Not Found- Advisory
updated_at:2026-09-19T01:21:39Z
Request
Could the curation team review this published repository advisory for inclusion in the global GitHub Advisory Database?
I have not requested a CVE because database inclusion and CVE assignment are separate. If a CVE or additional information is required for curation, please advise.
- Dominant language
- No language data
- Stars
- 2.5k
- Forks
- 772
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 46
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/advisory-database
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/advisory-database#9255 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#9164 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#8994 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/advisory-database#8898 · 4 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#8841 ·
All issues in github/advisory-database
Similar issues
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Nmap
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Azure/azure-functions-docker#1257 ·