AWS mcp-gateway-registry
Missing authorization on the external management API in mcp-gateway-registry enables privilege escalation to registry administrator
Missing authorization in the external management API in Amazon mcp-gateway-registry 1.0.9 through 1.24.7 might allow an authenticated remote user to assign the registry administrator scope to their own identity group and obtain administrative control of every registered gateway asset via a crafted group import request. To remediate this issue, users should upgrade to version 1.25.0.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.8high · scored by CNA · CWE-862
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
AWS mcp-gateway-registry
- >= 1.0.9, <= 1.24.7
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Patch github.com/agentic-community/mcp-gateway-regis…
- Vendor advisory github.com/agentic-community/mcp-gateway-regis…
- Vendor advisory aws.amazon.com/security/security-bulletins/2026-17…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.