---
title: AWS mcp-gateway-registry CVE-2026-125926: anyone allowed to register an MCP server could aim it at internal services and read the replies; fixed in 1.35.0 | ctxsec
url: https://ctxsec.com/items/aws-mcp-gateway-registry-cve-2026-125926-ssrf-upstream-address-1-35-0
description: "AWS says the open-source MCP registry/gateway did not validate a registered server's upstream address in versions 1.0.3 to 1.34.0, so an authenticated user with register/modify rights could make the gateway send requests to the deployment's internal network, in some cases returning the responses. Version 1.35.0 validates addresses on registration and change but does not touch configurations stored earlier. AWS notes that 1.25.0, which fixed the separate CVE-2026-100307 management-API flaw, is still affected by this one."
status: "official (AWS security bulletin 2026-180-AWS, Nov 11, 2026; GHSA-fc39-fwh3-wv5r); no in-the-wild use reported"
published: 2026-11-13
---

> AWS says the open-source MCP registry/gateway did not validate a registered server's upstream address in versions 1.0.3 to 1.34.0, so an authenticated user with register/modify rights could make the gateway send requests to the deployment's internal network, in some cases returning the responses. Version 1.35.0 validates addresses on registration and change but does not touch configurations stored earlier. AWS notes that 1.25.0, which fixed the separate CVE-2026-100307 management-API flaw, is still affected by this one.

[← Context & Harness Attacks](/context) · [markdown](/items/aws-mcp-gateway-registry-cve-2026-125926-ssrf-upstream-address-1-35-0.md)

official (AWS security bulletin 2026-180-AWS, Nov 11, 2026; GHSA-fc39-fwh3-wv5r); no in-the-wild use reported

2026-11-13 7:40 AM ET

### AWS mcp-gateway-registry CVE-2026-125926: anyone allowed to register an MCP server could aim it at internal services and read the replies; fixed in 1.35.0

- **After upgrading:** review every registered server's upstream address and remove anything you didn't intend; check logs from the vulnerable period for unexpected registrations or edits; if the registry has a cloud role and you can't rule out misuse, review that role's activity and rotate its credentials.
- **Until you can upgrade:** limit who can register/modify servers, restrict egress from the registry and auth-server components, and require IMDSv2 with least-privilege roles on EC2.

Sources: [AWS Security Bulletins: 2026-180-AWS CVE-2026-125926](https://aws.amazon.com/security/security-bulletins/) · [Rapid7 VulnDB: CVE-2026-125926](https://www.rapid7.com/db/vulnerabilities/cve-2026-125926/)
