highresolved

mcp-gateway-registry SSRF enables internal-service access (CVE-2026-125926)

AWS disclosed an SSRF flaw in mcp-gateway-registry's server registration and update API. An authenticated user permitted to register or modify a server could direct the gateway to internal services, including instance metadata, and in some cases receive the responses. Version 1.35.0 fixes the upstream-address validation.

mcp-gateway-registry centralizes discovery, access control and proxying for registered MCP tool assets. Before 1.35.0, its registration and update API did not validate a registered server's upstream address.

An authenticated user with permission to register or modify a server could configure an internal-network destination. The gateway could send the request and, in some cases, return the response, exposing services such as cloud instance metadata endpoints and their credentials.

AWS fixed the issue in version 1.35.0. Existing server configurations are not changed by the upgrade, so deployments that ran an affected version need the vendor's post-upgrade review as well as the version update.

Takeaway

Upgrade mcp-gateway-registry to 1.35.0 or later and review server configurations created before the upgrade. Registration and update rights can become a path to internal services when a gateway does not validate upstream destinations.

Sources

mcpmcp-gateway-registryCVE-2026-125926