An MCP gateway could be steered at the network it guards
AWS fixed a flaw in mcp-gateway-registry, an open-source tool that registers MCP servers and passes calls through to them. Anyone allowed to register or edit a server could set its address to a service inside the deployment’s own network; the gateway then sent requests there, and in some cases returned the answers. In a cloud deployment that can include the instance metadata service, which hands out credentials. Versions 1.0.3 to 1.34.0 are affected. Version 1.35.0 checks the address whenever a server is registered or changed.
Our read. The gateway trusted the one thing every MCP server says about itself: where it lives. Whatever a server declares is data until it has been checked, and an address is a declaration like any other. A Suncly test of the servers behind this gateway would not have found the flaw, because it sits in the gateway, not in them. The case the gateway’s own tests needed was a registration written by someone hostile.
Reported by GBHackers, from AWS security bulletin 2026-180-AWS (CVE-2026-125926)











