# CVE-2026-102242: Path Traversal via Symlink Following in allowedLocalRoots in MCP Toolbox for Databases

> Remote authenticated attackers can bypass directory restrictions via symbolic links to read or overwrite arbitrary local files outside permitted roots.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/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:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-3gp8-hjh6-xf3r

## What is CVE-2026-102242?

CVE-2026-102242 is a high-severity path traversal vulnerability in Google MCP Toolbox for Databases, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper link resolution (CWE-59 / CWE-22) in the allowedLocalRoots path validation in Google MCP Toolbox for Databases versions 1.2.0 through 1.9.0 allows a remote authenticated attacker with tool execution permissions to bypass directory boundary restrictions via symbolic links. Because path validation checks directories lexically without resolving symbolic links first, an attacker can access or overwrite arbitrary local files located outside the permitted root directories.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-102242 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102242 is a high-severity path traversal vulnerability in Google MCP Toolbox for Databases, published on 29 Sep 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-102242 in the wild and no public exploit code.

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

## Sources

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

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