Plan this weekVulnerabilities

Two flaws in the open-source MCP Gateway Registry let a low-privilege user become admin or reach internal services: update to 1.35.0

AWS published two bulletins on 11 November for mcp-gateway-registry, an open-source control plane for MCP servers and AI agents. CVE-2026-100307 (CVSS 8.8) lets any logged-in user make themselves registry administrator; CVE-2026-125926 (CVSS 8.5) lets a user who can register servers make the gateway call internal services. No attacks reported. Fixed in 1.25.0 and 1.35.0.

How urgent

Plan this week

Who is affected

Anyone running mcp-gateway-registry (agentic-community, Apache-2.0) below 1.35.0. CVE-2026-100307 affects 1.0.9 to 1.24.7 (fixed in 1.25.0); CVE-2026-125926 affects 1.0.3 to 1.34.0 (fixed in 1.35.0). Hosted services that do not run this registry are not affected

What to do

Upgrade to 1.35.0 or later; then review the mcp_scopes group mappings for an unauthorized admin mapping, the registered server addresses and the logs for POST /api/servers/groups/import; rotate registry-managed credentials and any cloud role the registry holds if you cannot rule out misuse

Published 12 Nov 2026 · Sources last checked 12 Nov 2026No. 82 / 87

What happened

On 11 November 2026 AWS published two security bulletins for mcp-gateway-registry, an open-source project (Apache-2.0, maintained under the agentic-community organization on GitHub) that describes itself as a control plane and gateway for MCP servers, agents and other AI assets, with an nginx gateway, a FastAPI registry and an auth server. Both flaws were reported by the same researcher, credited as "novice-22". The AWS bulletins label them "Important"; the GitHub advisories rate them High. Neither says it has been exploited.

The two flaws, according to the advisories

  • CVE-2026-100307, CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary 8.8 (versions 1.0.9 to 1.24.7, fixed in 1.25.0). The /api/servers/* management endpoints checked that you were logged in but not what you were allowed to do. Any authenticated user could send a request to /api/servers/groups/import that maps their own identity-provider group to the registry administrator scope. Admin status is worked out on each request, so it took effect immediately. An administrator can register, change and remove servers and agents, edit access groups and read stored backend credentials. The advisory says the sibling group routes and several server-changing routes had the same gap.
  • CVE-2026-125926, CVSS 8.5 (versions 1.0.3 to 1.34.0, fixed in 1.35.0). The registry did not validate the upstream address of a registered server. A user allowed to register or modify servers could point it at a service on the internal network, and in some cases the gateway returned the response. Depending on the network, that can include the cloud instance metadata service and the credentials it hands out.

How serious it is

High on paper, and both need a logged-in user, so the exposure is mostly from inside: a compromised or malicious account, or a registry open to many users. No attacks are reported, which is why we put it at "week" and not "act". If your registry is reachable by people you do not fully trust, or runs with a cloud role attached, treat it as more urgent.

What to do

  1. Upgrade to 1.35.0 or later. Fixes shipped in 1.25.0 (admin escalation) and 1.35.0 (SSRF). Note that 1.25.0 or later is still affected by the SSRF until 1.35.0.
  2. Check for an existing admin mapping. The advisory says the upgrade does not remove group mappings created earlier. Review group_mappings and ui_permissions in the mcp_scopes collection and remove any unauthorized mcp-registry-admin mapping.
  3. Review the registered servers for upstream addresses you did not set, and the HTTP logs for POST /api/servers/groups/import (and the sibling group routes) from non-administrators.
  4. If misuse cannot be ruled out, rotate the credentials the registry stores, and if a cloud role is attached review its activity and rotate it.
  5. If you cannot upgrade yet, use the workarounds in the advisories: limit the registration routes to trusted administrators at the proxy, restrict outbound network access from the registry, and on AWS require IMDSv2 and a minimal role.

What we could not confirm

We read both AWS bulletins and both GitHub advisories and the project's README, not the release notes, and we did not check the CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary records on NVD or MITRE. The advisories do not name a specific role needed for the SSRF, only that the user can register or modify servers. We have no information on how many deployments run this registry or whether it has been attacked. We did not test it.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks