Published:
Flaws in an MCP gateway and the AWS API MCP Server: the central access layer becomes the target
In short: On 10 and 11 November 2026 AWS published three security bulletins on MCP tooling. In the open-source gateway mcp-gateway-registry, a signed-in user could make the server fetch internal addresses (SSRF, CVSS 8.5, fixed in 1.35.0) or grant themselves admin rights (fixed in 1.25.0). In the AWS API MCP Server, the security policy wrongly let certain operations through (fixed in 1.5.1).
Many organisations put a gateway between their AI assistants and their MCP servers: one place for authentication, authorization and a list of approved servers. That exact layer featured in AWS's bulletins this week. The mcp-gateway-registry project (GitHub organisation agentic-community) received two bulletins on 11 November, and the AWS API MCP Server from awslabs/mcp one on 10 November. None of the bulletins reports active exploitation.
What is wrong in mcp-gateway-registry?
CVE-2026-125926 — server-side request forgery. Through the API used to register or update servers, a user could make the registry send requests to addresses of their choosing. According to the GitHub advisory (GHSA-fc39-fwh3-wv5r), depending on the network setup those could include the cloud instance metadata service and the credentials it provides.
- Affected: 1.0.3 through 1.34.0. Fix: 1.35.0 (11 November).
- Severity: CVSS 3.1 8.5 (high) per the GitHub advisory; AWS classifies the bulletin as "Important". The attacker does need an account allowed to register or modify servers.
- Interim: restrict that permission to trusted accounts, limit outbound traffic from the registry and auth-server components, and on EC2 require IMDSv2 with least-privilege roles.
- After upgrading: the upgrade does not change server configurations stored earlier. AWS advises reviewing registered upstream addresses and logs, and rotating credentials of any attached cloud role if misuse cannot be ruled out.
CVE-2026-100307 — missing authorization. A signed-in, low-privileged user could send a crafted POST /api/servers/groups/import request that mapped their own identity-provider group to the registry administrator scope. It took effect on the next request, without re-authenticating. Versions 1.0.9 through 1.24.7 are affected; the fix already shipped in 1.25.0 (27 June 2026). Again, upgrading does not remove group mappings created while vulnerable.
What went wrong in the AWS API MCP Server?
The AWS API MCP Server lets an AI assistant call AWS APIs. Administrators can use a custom security policy to block operations (denyList) or require confirmation first (elicitList). According to bulletin 2026-176-AWS (CVE-2026-125271), operation names containing consecutive capital letters never matched those lists. The GitHub advisory gives examples such as creating a federated identity provider, deactivating an MFA device and deleting database clusters.
- Affected:
awslabs.aws-api-mcp-server0.2.13 up to 1.5.1, run locally with a custom policy. The remote AWS offering and theREAD_OPERATIONS_ONLYandREQUIRE_MUTATION_CONSENTsettings are not affected. - Severity: CVSS 4.0 8.5 (high) per the GitHub advisory. Fix: 1.5.1. AWS: there is no workaround other than upgrading.
In late October we covered the OAuth audience flaw in the same server, fixed in 1.6.0. If you already applied that update, you have this fix too.
Why should organisations pay attention?
A gateway is meant as a security control: it centralises access and makes policy enforceable. That also makes it the most valuable target in the chain. The gateway has network access to internal systems, often a cloud role, and decides who is an administrator. An SSRF or authorization bug there does not affect one tool but everything behind it. The same goes for a deny list: it gives a sense of control, but only protects as long as the name matching is right.
The timing of CVE-2026-100307 also stands out: fixed in June, publicly disclosed in November. If you only wait for bulletins and don't track which version you run, you can operate with a known flaw for months without knowing.
Our advice
(1) Running mcp-gateway-registry: upgrade to 1.35.0, review registered upstream addresses and any group mappings to admin scope, and rotate the credentials of an attached cloud role if you cannot rule out misuse. (2) Using the AWS API MCP Server locally: upgrade to at least 1.6.0. (3) Treat any MCP gateway as a crown jewel: least privilege, restricted egress, IMDSv2 and logging of changes to server registrations. (4) Don't rely on a deny list alone for dangerous operations; combine it with minimal IAM permissions and, where possible, read-only mode. See also MCP security & watch-outs and MCP servers for cloud and infrastructure.
The bigger picture: after flaws in individual servers, SDKs and developer tools, the management layer is now in the spotlight. That makes sense: the more companies expose MCP centrally, the more attractive that central layer becomes. If you build your own MCP server or gateway, SSRF protection and per-route authorization should be standard test items.
Sources
- AWS Security Bulletin 2026-180-AWS — CVE-2026-125926, SSRF in mcp-gateway-registry (11 November 2026)
- GHSA-fc39-fwh3-wv5r — mcp-gateway-registry SSRF, CVSS 3.1 8.5 (GitHub, 11 November 2026)
- mcp-gateway-registry release 1.35.0 (GitHub)
- AWS Security Bulletin 2026-179-AWS — CVE-2026-100307, missing authorization in mcp-gateway-registry (11 November 2026)
- AWS Security Bulletin 2026-176-AWS — CVE-2026-125271, AWS API MCP Server policy bypass (10 November 2026)
- GHSA-4wq9-grf3-qg2p — AWS API MCP Server, CVSS 4.0 8.5 (GitHub, 10 November 2026)
- Cyber Security News — AWS MCP Gateway Security Flaw (12 November 2026)
Frequently asked questions
Which version of mcp-gateway-registry is safe?
Version 1.35.0 (11 November 2026) fixes the SSRF flaw CVE-2026-125926; versions 1.0.3 through 1.34.0 are affected. The authorization flaw CVE-2026-100307 has been fixed since 1.25.0 (27 June 2026). Note that upgrading does not correct server configurations or group mappings stored earlier. You need to review those yourself.
Do I need to update the AWS API MCP Server?
Yes, if you run it locally with a custom security policy (denyList or elicitList). Versions 0.2.13 up to 1.5.1 let operation names with consecutive capital letters slip past the policy. There is no workaround other than upgrading. Go straight to 1.6.0 or later, which also fixes the OAuth audience flaw from October. The remote, AWS-hosted offering is not affected.
What is an MCP gateway and why is a flaw in one especially serious?
An MCP gateway sits between AI clients and an organisation's MCP servers. It controls who may use which server and tool, and often keeps a registry of approved servers. Because all traffic passes through it and it holds network access and credentials, a flaw in the gateway exposes far more than a single tool.
Last updated: