MCP gateway registry bug let any logged-in user make themselves admin over every registered MCP server and read its stored credentials; update to 1.25.0
- Upgrading isn't enough: 1.25.0 doesn't undo group mappings written before the upgrade or invalidate credentials already read. Review the
mcp_scopescollection's group mappings for unexpected admin scopes for the whole period you ran an affected version, and rotate backend credentials the registry managed. - Also gated by the fix: sibling group routes (create, add, remove, delete) and server register, toggle, auth-credential update and version routes.
- Patch forks and derivative deployments too.
- Lesson: an MCP gateway is a credential vault and a control plane for every agent behind it; give its admin API the same authorization tests as any IAM system.
Sources: AWS Security Bulletin 2026-179-AWS: CVE-2026-100307, mcp-gateway-registry · GitHub advisory GHSA-rxf3-qgpv-wxvr (agentic-community/mcp-gateway-registry)