AAK-MCP-GATEWAY-REGISTRY-CVE-2026-100307-001: Amazon mcp-gateway-registry image 1.0.9 to 1.24.7: any signed-in user can map their group to the registry admin scope
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/container_image_pins.py- Auto-fixable
- No.
- SARIF name
McpGatewayRegistryGroupImportAdminEscalation
What it detects
Amazon's MCP Gateway & Registry (agentic-community/mcp-gateway-registry) decides which identities reach which registered MCP servers and agents. Its registry service ships as the image public.ecr.aws/p3v1o3c6/registry and, up to 1.24.4, as Docker Hub's mcpgateway/registry. From 1.0.9 the external management API's POST /api/servers/groups/import authenticated the caller but checked no role, so any signed-in user could import a group definition that maps their own identity-provider group to the mcp-registry-admin scope, be treated as an administrator from the next request, and then register, change or remove every server and agent and read the backend credentials the registry stores (CVE-2026-100307, CVSS 3.1 8.8, CWE-862, GHSA-rxf3-qgpv-wxvr). The sibling group routes and several server-mutation routes had the same gap. Checked in the source at the git tag each image's label names: v1.0.8 has no import route; v1.0.9, v1.0.22-p1 and 1.24.7 run import_group_definition with no admin check; 1.25.0 calls _require_admin first (mcp-gateway-registry#1333).
How to fix
Run public.ecr.aws/p3v1o3c6/registry 1.25.0 or later, pinned by version. Docker Hub's mcpgateway/registry has no fixed tag, so move to the ECR Public image. Upgrading does not undo a grant made before it: review the mcp_scopes collection's group_mappings for mappings to mcp-registry-admin or another privileged scope, and its ui_permissions for mutating actions granted to all, remove any an administrator did not create, and rotate the credentials the registry stores where unintended access cannot be ruled out.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-GATEWAY-REGISTRY-CVE-2026-100307-001
Limitations
Reads image references only: an image: value or any other mention of public.ecr.aws/p3v1o3c6/registry:TAG or mcpgateway/registry:TAG in YAML (compose files, Kubernetes manifests, MCP configs), a Helm values mapping whose repository names the whole image beside a tag, Dockerfile and Containerfile FROM, and docker run arguments in *mcp*.json and claude_desktop_config.json. The project's auth-server and mcpgw images are not read: the management API is the registry service's. Tags from 1.0.9 below 1.25.0 are reported, v1.0.9-patch1, v1.0.22-p1 and the two-part 1.0, 1.23 and 1.24 among them; tags below 1.0.9 predate the import route and are not. Docker Hub's latest is the 1.24.4 build, so an untagged mcpgateway/registry is reported; ECR Public's latest was the 1.37.0 digest on 2026-11-12, so an untagged ECR Public reference is not. The one-part tag 1 states no version and is not reported, although Docker Hub's is the v1.0.12 build. The project's own charts split the image into registry: public.ecr.aws/p3v1o3c6 and repository: registry, and set the tag in global.image.tag, and its compose file interpolates both (${ECR_REGISTRY:-...}/registry:${REGISTRY_VERSION:-latest}), so neither is read, and neither are Terraform variables. A reference to the GitHub repository, which AAK-MCP-GATEWAY-REGISTRY-CVE-2026-14471-001 reads, is not read by this rule. The rule reads the tag, not the scope store, so it cannot tell whether a grant made before an upgrade is still in place. docker.io/mcpgateway/registry and mirrors under another registry are not matched, and commented-out lines are skipped.
References
- CVE: CVE-2026-100307
- OWASP MCP Top 10: MCP02:2025 (Privilege Escalation via Scope Creep), MCP07:2025 (Insufficient Authentication & Authorization), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-08 (MCP-Specific Vuln)
- CSA AI Controls Matrix (AICM): IAM-01, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-GATEWAY-REGISTRY-CVE-2026-100307-001.md: the page then shows that text, with the registry reference appended under it.