Skip to content

AAK-MCP-GATEWAY-REGISTRY-CVE-2026-125926-001: Amazon mcp-gateway-registry image 1.0.3 to 1.34.0: a registered server's address can point the gateway at internal services

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
McpGatewayRegistryUpstreamAddressSsrf

What it detects

Amazon's MCP Gateway & Registry (agentic-community/mcp-gateway-registry) proxies MCP traffic to the servers registered with it. Its registry service ships as the image public.ecr.aws/p3v1o3c6/registry and, up to 1.24.4, as Docker Hub's mcpgateway/registry. Before 1.35.0 a user allowed to register or modify a server could set its upstream address to a service on the deployment's internal network or to the cloud instance metadata endpoint, and the gateway sent requests there and in some cases returned the responses (CVE-2026-125926, CVSS 3.1 8.5, CWE-918, GHSA-fc39-fwh3-wv5r). Checked in the source at the git tags: v1.0.3 to 1.25.0 store a registered address with no check; 1.26.0 refuses a literal private or metadata address at registration and update but resolves no host name (validate_proxy_pass_url), unchanged in 1.35.0. The advisory names no fix commit. The 1.35.0 change on this path is mcp-gateway-registry#1795: a virtual server stops routing to a backend that is disabled or not healthy, as the direct route already did, so a backend the health check's address guard refused is no longer reachable through one. The range is the advisory's, v1.0.3 through 1.34.0.

How to fix

Run public.ecr.aws/p3v1o3c6/registry 1.35.0 or later, pinned by version. Docker Hub's mcpgateway/registry has no fixed tag, so move to the ECR Public image. 1.35.0 leaves stored server addresses as they were: review every registered server's upstream address and remove any you did not intend. Limit registering and modifying servers to trusted accounts, restrict the registry's and auth server's outbound network access to the destinations they need, require IMDSv2 on EC2, and rotate the attached role's credentials if the logs cannot rule out unexpected registrations.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-GATEWAY-REGISTRY-CVE-2026-125926-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 registration and update API is the registry service's. Tags from 1.0.3 below 1.35.0 are reported, the two-part 1.0 to 1.34 among them, which is every version tag on Docker Hub from v1.0.3. Docker Hub's v1.0.0 to v1.0.2 and 1.0.0 builds predate the advisory's first release and are not reported, although their registration route checks no address either. 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. Tags from 1.0.9 below 1.25.0 also fire AAK-MCP-GATEWAY-REGISTRY-CVE-2026-100307-001, a different flaw. 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 stored server addresses, so it cannot tell whether an address registered before an upgrade still points inside the network. docker.io/mcpgateway/registry and mirrors under another registry are not matched, and commented-out lines are skipped.

References


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-125926-001.md: the page then shows that text, with the registry reference appended under it.