Repository advisory GHSA-7v25-vcp6-4hcr not in global Advisory Database

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.

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: null
• submission.accepted: false
• GET /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.