Skip to main content
Mallory
MediumVulnerability

CVE-2026-125926: SSRF in Amazon mcp-gateway-registry Server Registration and Update API

Published Nov 11, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days9 mentions · peak 4 in a dayToday
CVSS6.3Medium · v4
EPSS0.35%29th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-125926CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2026-125926 is a server-side request forgery vulnerability in upstream-address validation in the server registration and update API of Amazon mcp-gateway-registry versions 1.0.3 through 1.34.0. An authenticated user authorized to register or modify servers can supply a crafted upstream address that causes the gateway to request internal network services or cloud instance metadata endpoints. In some cases, the gateway returns the destination's response to the user, exposing information otherwise inaccessible directly. Version 1.35.0 fixes validation during registration and modification but does not modify previously stored server configurations.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation allows requests from the gateway's network position to internal services, potentially bypassing network-access restrictions that apply to the attacker. Returned responses can disclose internal service information. If accessible, insufficiently protected cloud instance metadata may expose temporary credentials for an attached cloud role; subsequent access depends on that role's permissions. Actual impact depends on gateway connectivity, destination protections, and whether responses are returned. Active exploitation and credential theft have not been confirmed.

Mitigation

If you can’t patch tonight, do this now.

Restrict server registration and modification permissions to trusted accounts. Limit outbound connectivity from the registry and auth-server components to required destinations. Require IMDSv2 on Amazon EC2 and apply least-privilege permissions to attached cloud roles. These compensating controls do not replace upgrading and reviewing existing server configurations.

Remediation

Patch, then assume compromise.

Upgrade to mcp-gateway-registry 1.35.0 or later, and incorporate the corresponding fix into forks and derived projects. Review all existing registered upstream addresses after upgrading and correct or remove unintended destinations, because the fix leaves stored configurations unchanged. Examine application logs from the affected deployment period for unexpected server registrations or upstream-address modifications. If an attached cloud role exists and unexpected activity cannot be ruled out, review the role's activity and rotate its credentials. Version 1.25.0 fixes a separate issue and does not remediate this vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-125926 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-125926 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-125926?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-125926.
Is there a patch for CVE-2026-125926?
Upgrade to mcp-gateway-registry 1.35.0 or later, and incorporate the corresponding fix into forks and derived projects. Review all existing registered upstream addresses after upgrading and correct or remove unintended destinations, because the fix leaves stored configurations unchanged.
How severe is CVE-2026-125926?
CVE-2026-125926 has a CVSS v4 score of 6.3 (Medium) and an EPSS score of 0.35% (29th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cyber security newsNews · Nov 12, 2026AWS MCP Gateway Security Flaw Allowing Access to Internal Networks and Cloud CredentialsA server-side request forgery vulnerability in mcp-gateway-registry allows an authenticated user with server registration or modification permissions to supply a crafted upstream address, causing the gateway to contact internal services and potentially return their responses. Impact depends on network reachability; exposure of cloud role credentials is a potential risk, not a confirmed outcome. Version 1.35.0 fixes address validation but does not change previously stored configurations. Administrators should upgrade, review existing upstream addresses and logs, restrict registration and editing permissions, limit outbound connectivity, require IMDSv2 on EC2, and minimize attached role permissions.Read more ↗cryptika blogNews · Nov 12, 2026AWS MCP Gateway Security Flaw Allowing Access to Internal Networks and Cloud Credentials | Cryptika CybersecurityA server-side request forgery vulnerability in AWS mcp-gateway-registry allows authenticated users with server registration or modification permissions to supply crafted upstream addresses, causing the gateway to request internal services and, in some cases, return their responses. Impact depends on the gateway's network access; cloud-role credentials may also be at risk, but credential theft and active exploitation are not confirmed. Version 1.35.0 fixes address validation for registrations and modifications but does not sanitize previously stored configurations. Administrators should upgrade and review existing upstream addresses. Interim mitigations include restricting registration and editing permissions, limiting outbound connections, requiring EC2 IMDSv2, and minimizing attached role permissions.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.