AWS MCP Gateway Registry Fix Requires Privilege and Credential Review
Tech GuruQuick Answer
Upgrade affected registries, then inspect stored privilege mappings and registered assets. Review management API logs and rotate registry-managed credentials at their source if unintended access cannot be excluded.
Confirm Scope And Apply The Supported Remediation
What to do now: Record registry versions, forks, identity groups, management API exposure, stored credentials and deployment dates. Match versions 1.0.9–1.24.7 and the period each was deployed. Review all affected management mutation routes, including group import and sibling group operations. Apply 1.25.0 or a later supported release containing this fix. Review mcp_scopes group_mappings and ui_permissions; remove grants not created by an administrator. Inspect registered servers and agents for unintended changes, and rotate registry-managed credentials if access cannot be excluded, including when logs are incomplete. Confirm non-administrators cannot mutate protected groups or assets; verify approved mappings and upstream URLs. Correlate management requests with identity and subsequent asset changes, and retain the audit results.
Last verified: 2026-11-12 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Amazon mcp-gateway-registry external management API |
|---|---|
| Advisory | 2026-179-AWS / GHSA-rxf3-qgpv-wxvr |
| CVE | CVE-2026-100307 |
| Authoritative release date | November 11, 2026 at 12:30 PST (20:30 UTC), from AWS bulletin 2026-179-AWS. |
| Authority revision date | No separate revision date is provided by the authority. |
| Affected versions | mcp-gateway-registry 1.0.9 through 1.24.7 inclusive. Exploitation requires an authenticated low-privileged user. |
| Fixed version | mcp-gateway-registry 1.25.0 or later for CVE-2026-100307 |
| CVSS base score | 8.8 (CVSS v3.1 base score, project advisory) |
| CVSS severity | High |
| Exploitation status | The cited AWS and project advisories do not confirm exploitation in the wild.; no exploitation claim is inferred. |
What Changed
AWS discloses missing authorization that lets a low-privileged account gain registry administrator access. The software fix blocks the write path but leaves earlier privilege grants and exposed credentials unchanged.
What To Validate Now
- Inventory. Record registry versions, forks, identity groups, management API exposure, stored credentials and deployment dates.
- Establish applicability. Match versions 1.0.9–1.24.7 and the period each was deployed. Review all affected management mutation routes, including group import and sibling group operations.
- Remediate. Apply 1.25.0 or a later supported release containing this fix. Review mcp_scopes group_mappings and ui_permissions; remove grants not created by an administrator. Inspect registered servers and agents for unintended changes, and rotate registry-managed credentials if access cannot be excluded, including when logs are incomplete.
- Validate. Confirm non-administrators cannot mutate protected groups or assets; verify approved mappings and upstream URLs. Correlate management requests with identity and subsequent asset changes, and retain the audit results.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
An upgrade does not revoke previously stored administrator grants or invalidate previously read secrets. Restrict mutation routes to trusted administrators until patched. Version 1.25.0 does not fix the separate SSRF issue in 2026-180-AWS; that issue requires 1.35.0 or later.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
