← All updates

Security / News explained

MCP registry authorization fixes leave stored permissions to review

A November 11 disclosure explains an authorization flaw fixed in June. Upgrading closes the write path, while old group grants and potentially exposed credentials need separate review.

By Zyel · Published · 4 min read

AWS disclosed CVE-2026-100307 on November 11, 2026: an authorization flaw in the open-source mcp-gateway-registry affecting versions 1.0.9 through 1.24.7, inclusive. An authenticated user with limited privileges could obtain registry administrator access. The practical consequence reaches beyond installing the fixed software. [1]

Our reading is that the recovery question has two parts: can an ordinary account create a privileged grant now, and did an earlier grant survive? A clean answer to the first question cannot settle the second. Permissions have a longer memory than a deployment job.

The login check answered only half the question

The maintainers describe management endpoints that checked the caller's identity without enforcing the required role or permission. A group-import operation could store a privileged mapping. Because the registry calculated administrator status on each request, the changed mapping could elevate that same identity on its next request. [2]

The resulting authority included management of registered servers and agents, access-control changes, and access to backend credentials and configuration held by the registry. The missing checks also affected related group operations and several server-changing operations; this was broader than a single button in the browser interface. [2]

Consider a hypothetical employee who is allowed to discover approved tools but cannot administer them. A valid company login establishes who that employee is. It should not authorize a request that rewrites the rules deciding who administers the tool directory. That distinction matters even when the employee never sees an administrator screen.

OWASP treats authentication and authorization as separate decisions. Its guidance calls for checking permissions on every request, denying access by default, and enforcing checks in the right place. Hiding a control in a user interface cannot supply the missing decision at an API boundary. [4]

A June fix, a November disclosure

Version 1.25.0 was already released in June 2026. Its release notes explicitly describe authorization enforcement on external management endpoints and warn that callers relying on the earlier behavior will receive authorization errors. The November advisory is new disclosure of that older fix, rather than a claim that the patch first became available this week. [3]

The maintainers also identify an important limit: the patch changes authorization on the write path, while previously stored group definitions remain. An unauthorized privileged mapping can therefore continue granting administrator access after an upgrade. The release does not invalidate credentials that someone may already have read. [2]

That is why a healthy application restart is incomplete evidence of recovery. The running program and its saved access rules are different things. Our interpretation is that closing the defect and reviewing the state it could have changed belong in the same response, with a clear owner for each.

The review follows the stored authority

AWS directs affected operators to inspect group mappings and broad write permissions in the scope store. In the documented mcp_scopes collection, the relevant fields include group_mappings and ui_permissions. Grants that were not created by an administrator should be removed; reinstalling the application does not perform that cleanup. [1]

The bulletin also calls for reviewing HTTP logs across the period an affected version was deployed. Group-import requests from non-administrators, related group changes and server-changing requests deserve attention. Correlating later requests from the same identity helps establish what that authority was used to change. [1]

Potential credential exposure needs its own decision. The maintainers say registry administrators can read stored backend authentication material. Where unintended access cannot be excluded, those credentials need rotation at their source systems; unavailable or incomplete historical logs are specifically a reason to rotate them. [2]

For a team reviewing its own deployment, useful answers would identify which grants were examined, who approved them, which connected systems hold the original credentials, and what evidence covers the exposure period. These are proposed review questions, not findings about any customer, employee or production environment.

A repaired permission check still needs a version decision

For deployments awaiting an upgrade, AWS recommends restricting management mutations at the ingress or proxy layer to trusted administrators and monitoring unexpected scope changes. Those measures limit further access while the upgrade is pending. They do not remove older grants or replace the historical review. [1]

A separate November 11 bulletin covers CVE-2026-125926, an unrelated upstream-address flaw fixed in version 1.35.0. The earlier authorization fix in 1.25.0 does not cover that issue. Operators should choose a current release addressing both advisories, and check forks or derivative code for the corresponding fixes. [5]

The broader engineering lesson is straightforward: access rules are application data with security consequences. A patch can improve every future permission decision while leaving yesterday's unwanted decision in the database. Closing the work means understanding both the code now running and the authority it will read on the next request.

Sources + further reading

Source dates describe the original material. Publication above is the date this Zyel article went live.

  1. 2026-179-AWS: Missing authorization in mcp-gateway-registryAWS Security Bulletins · Checked Nov 12, 2026
  2. GHSA-rxf3-qgpv-wxvr: Missing authorization enables gateway administrator escalationmcp-gateway-registry maintainers · Checked Nov 12, 2026
  3. mcp-gateway-registry 1.25.0 release notesmcp-gateway-registry maintainers · Checked Nov 12, 2026
  4. Authorization Cheat SheetOWASP Cheat Sheet Series · Checked Nov 12, 2026
  5. 2026-180-AWS: Separate upstream-address request-forgery issueAWS Security Bulletins · Checked Nov 12, 2026

Reader discussion

What would you ask next?

Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.

No reader comments yet.

10–2,000 characters. Plain text. Leave out passwords, private project data and personal contact details. A blank display name appears as Anonymous.

Complete the CAPTCHA before sending. Verification runs on your device.