# CVE-2026-16481: Server-side request forgery in MCP Toolbox for Databases (googleapis/mcp-toolbox)

> Attackers can exploit SSRF in the FHIR fetch tool to exfiltrate OAuth tokens and access Protected Health Information via unvalidated URL parameters.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-qr8r-mqp7-36xx

## What is CVE-2026-16481?

CVE-2026-16481 is a medium-severity server-side request forgery vulnerability in MCP Toolbox for Databases (googleapis/mcp-toolbox), published on 27 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) and credential exfiltration vulnerability exists in the cloud-healthcare-fhir-fetch-page tool of googleapis/mcp-toolbox.

The tool takes an unvalidated pageURL parameter from the client and issues an HTTP GET request to it using an authenticated client. The underlying transport automatically attaches an Authorization: Bearer  header to every outbound request regardless of the destination host. An attacker can supply an arbitrary external URL to the pageURL parameter (either directly via the tool execution payload or implicitly via data-driven pagination tracking loops), leading Toolbox into sending its OAuth/service-account access token to an attacker-controlled listener. Depending on the configuration, this leaks either the end-user's token or the broader service-account access token (ADC), potentially exposing Protected Health Information (PHI) and secondary Google Cloud Platform services.

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

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

It affects 1 product.


Products: Google Mcp Toolbox for Databases.

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

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

## Is CVE-2026-16481 being exploited?

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

## Other vulnerabilities in MCP Toolbox for Databases (googleapis/mcp-toolbox)

- [CVE-2026-11720](https://insights.sbomify.com/CVE-2026-11720/): Path Traversal in googleapis/mcp-toolbox HTTP Tool URL Builder (critical 9.3)
- [CVE-2026-11717](https://insights.sbomify.com/CVE-2026-11717/): googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken) (critical 9.3)
- [CVE-2026-11718](https://insights.sbomify.com/CVE-2026-11718/): googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken) (critical 9.3)
- [CVE-2026-15829](https://insights.sbomify.com/CVE-2026-15829/): SQL Injection and Security Boundary Bypass in googleapis/mcp-toolbox (high 8.6)
- [CVE-2026-11719](https://insights.sbomify.com/CVE-2026-11719/): MCP Toolbox for Databases: authenticated authorization bypass (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16481 is a medium-severity server-side request forgery vulnerability in MCP Toolbox for Databases (googleapis/mcp-toolbox), published on 27 Jul 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-16481 in the wild and no public exploit code.

Affected product: MCP Toolbox for Databases (googleapis/mcp-toolbox). 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-16481/ (Markdown: https://insights.sbomify.com/CVE-2026-16481/index.md)
```

## Sources

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

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