AWS mcp-gateway-registry CVE-2026-125926: anyone allowed to register an MCP server could aim it at internal services and read the replies; fixed in 1.35.0
- After upgrading: review every registered server's upstream address and remove anything you didn't intend; check logs from the vulnerable period for unexpected registrations or edits; if the registry has a cloud role and you can't rule out misuse, review that role's activity and rotate its credentials.
- Until you can upgrade: limit who can register/modify servers, restrict egress from the registry and auth-server components, and require IMDSv2 with least-privilege roles on EC2.
Sources: AWS Security Bulletins: 2026-180-AWS CVE-2026-125926 · Rapid7 VulnDB: CVE-2026-125926