InformationalVulnerabilityPatch available

Cyber Security News reports AWS MCP gateway SSRF flaw, fix in 1.35.0

Cyber Security News reports AWS disclosed an SSRF flaw in mcp-gateway-registry; upgrade to 1.35.0 and review stored upstream addresses.

Published
Fixed in
mcp-gateway-registry 1.35.0
Exploitation
No evidence reported. Per Cyber Security News, the AWS bulletin does not confirm credential theft or active exploitation of this flaw.

Live scores

CVE-2026-125926
EPSS
0.003
low predicted chance of attack
VEDAS
0.056
little exploit evidence
On CISA KEV
Not listed
Detection rule
No public rule yet
EPSS (chance of attack)
100.1CVE-2026-125926 EPSS over time2026-112026-11-17
VEDAS (exploit evidence)
100.5CVE-2026-125926 VEDAS over time2026-112026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

What happened

According to Cyber Security News, AWS has fixed a server-side request forgery (SSRF) flaw in mcp-gateway-registry, tracked as CVE-2026-125926. The outlet says AWS disclosed it on November 11, 2026 and urged users to upgrade. The AWS bulletin itself was not among our sources, so everything below is as relayed by Cyber Security News.

Cyber Security News describes the project as an open-source registry and gateway for Model Context Protocol servers, covering server discovery, access control and tool proxying. It reports that the flaw lies in how the registry checks the upstream address supplied when a user registers or updates a server. The outlet says a user with a valid account and permission to register or modify servers could set a crafted address and make the gateway send requests to services inside the deployment’s network. It adds that in some cases the gateway also returned the responses, so the user could read information from those services.

The outlet stresses this is not an unauthenticated attack against every exposed gateway, and says the impact depends on which services the deployment can reach. It also says that if the gateway runs with an attached cloud role, SSRF can expose temporary role credentials through unprotected metadata access, citing related EC2 metadata attacks. According to the outlet, the AWS bulletin does not confirm credential theft or active exploitation of this specific flaw. It credits researcher novice-22 for coordinated disclosure.

Not confirmed in the source: any in-the-wild exploitation, any affected victim, and a severity rating or CVSS score.

Am I affected?

According to Cyber Security News:

  • Versions 1.0.3 through 1.34.0 are affected. Version 1.35.0 contains the fix.
  • A separate flaw in the external management API was fixed in 1.25.0. That update does not protect against CVE-2026-125926, so deployments on 1.25.0 through 1.34.0 remain affected.
  • Forks and derived projects also need the fix.
  • An attacker must already have a valid account with permission to register or modify servers.
  • Per the AWS bulletin as cited by the outlet, version 1.35.0 checks upstream addresses at registration and modification, but leaves previously stored server settings unchanged.

What to do now

  1. Upgrade mcp-gateway-registry to 1.35.0 or later, including any forks or derived projects. Cyber Security News says AWS urged users to upgrade and that 1.35.0 is the minimum fixed release.
  2. After upgrading, review existing upstream addresses and correct or remove any destination you did not intend to allow. Cyber Security News gives this as advice to administrators, not as an AWS recommendation.
  3. Examine application logs covering the time an affected version was running, and review unexpected server registrations or address changes. The outlet also presents this as general advice to teams.
  4. If the registry has an attached cloud role and the logs cannot rule out unexpected activity, the outlet says AWS advises checking that role’s activity and rotating its credentials.
  5. If you cannot patch immediately, the outlet says AWS recommends:
    • limiting registration and editing rights to trusted accounts;
    • restricting outbound connections from the registry and auth-server components;
    • requiring IMDSv2 on EC2;
    • reducing attached role permissions.

According to the outlet, these mitigations do not replace upgrading and reviewing stored configurations.

Sources