CVE-2026-125926: AWS mcp-gateway-registry · Server-Side Request Forgery
Affects AWS mcp-gateway-registrySource CVE Database V5
Not known to be exploited · CVSS 8.5 High · patch available : patch AWS mcp-gateway-registry soon.
Data as of 11 Nov 2026, 21:32 UTC
Thin evidence
One scorer or none| CNA (AMZN) | CVSS 3.1 | 8.5 |
|---|---|---|
| CNA (AMZN) | CVSS 4.0 | 6.3 |
- Patch
- Available
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWSmcp-gateway-registry | Affected
| Fixed in– |
AI-suggested
AWS has released version 1.35.0 of mcp-gateway-registry to remediate this SSRF vulnerability. Users should upgrade to version 1.35.0 or later. Since this is a cloud service, AWS manages remediation for the cloud-hosted components. Check the AWS security bulletin at https://aws.amazon.com/security/security-bulletins/2026-180-aws/ for official guidance and confirmation of patch status.
Description
CVE-2026-125926 is a server-side request forgery (SSRF) vulnerability in the server registration and update API of Amazon's mcp-gateway-registry prior to version 1.35.0. An authenticated remote user could exploit this flaw to send requests from the gateway to internal network services and cloud instance metadata endpoints, potentially reading sensitive responses. The vulnerability has a high severity with a CVSS score of 8.5. AWS has released version 1.35.0 to address this issue.