# CVE-2026-125926: Server-side request forgery in the server registration and update API in mcp-gateway-registry

> Authenticated users can make the gateway send requests to internal services and cloud metadata endpoints and read responses.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026

## What is CVE-2026-125926?

CVE-2026-125926 is a medium-severity server-side request forgery vulnerability in AWS mcp-gateway-registry, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-side request forgery (SSRF) in the server registration and update API in Amazon mcp-gateway-registry before 1.35.0 might allow an authenticated remote user to send requests from the gateway to internal network services and cloud instance metadata endpoints and read the responses via a crafted request.

To remediate this issue, users should upgrade to version 1.35.0.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-125926?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-125926?

No fix has been published for CVE-2026-125926 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125926 being exploited?

There is no known exploitation of CVE-2026-125926 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125926 and fix it if it is affected.

What it is: CVE-2026-125926 is a medium-severity server-side request forgery vulnerability in AWS mcp-gateway-registry, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-125926 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: AWS mcp-gateway-registry. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125926/ (Markdown: https://insights.sbomify.com/CVE-2026-125926/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125926
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125926
- OSV: https://osv.dev/vulnerability/CVE-2026-125926

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125926/
Summaries are generated and may contain mistakes; the official description above is the record.