AWS mcp-gateway-registry SSRF fixed in 1.35.0 (CVE-2026-125926)
Original title: AWS MCP Gateway Security Flaw Allowing Access to Internal Networks and Cloud Credentials
An authenticated user who can register servers could make the gateway query internal services; exploitation is not confirmed.
AWS fixed a server-side request forgery flaw in the open-source mcp-gateway-registry, tracked as CVE-2026-125926. Versions 1.0.3 through 1.34.0 are affected, and version 1.35.0 adds checks on upstream addresses during server registration and modification. A user who already can register or edit servers could point the gateway at internal services and, in some cases, read responses. AWS disclosed the issue on November 11, 2026, credited researcher novice-22, and did not confirm credential theft or active exploitation.
Unconfirmed: AWS does not confirm that cloud credentials were stolen or that the flaw has been exploited.
- Stored server settings are not changed by the 1.35.0 upgrade.
- A separate management-API flaw fixed in 1.25.0 does not cover this CVE.
- Deployments from 1.25.0 through 1.34.0 remain affected.
- If patching is delayed, AWS suggests limiting who can register servers and restricting outbound connections.
Impact: Authenticated user can reach and sometimes read internal services
| Product | Affected | Fixed in |
|---|---|---|
| AWS mcp-gateway-registry | 1.0.3 through 1.34.0 | 1.35.0 |
- 1.Upgrade mcp-gateway-registry to version 1.35.0.
- 2.Review stored upstream addresses and remove destinations that were not intended.
- 3.If logs cannot rule out unexpected use of an attached cloud role, rotate its credentials.
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-125926 | Authenticated SSRF in Amazon mcp-gateway-registry before 1.35.0 | 6.3 | — |
From the original article
2 min read at cybersecuritynews.com
AWS has fixed a server-side request forgery flaw in mcp-gateway-registry that could let an authenticated attacker reach internal services through the gateway. Tracked as CVE-2026-125926, the issue affects versions 1. 0.
By Guru Baran · cybersecuritynews.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.