# CVE-2026-81102: Dropbox Dash MCP Server DNS Rebinding via Missing Host Header Validation

> An attacker can use DNS rebinding to access the local Dropbox Dash MCP server and invoke tools via a victim's browser.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** GHSA-37q3-f6jc-625w

## What is CVE-2026-81102?

CVE-2026-81102 is a low-severity server-side request forgery vulnerability in dropbox mcp-server-dash, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Dash MCP server bound its listener to the loopback address but never checked the host a request named. src/mcp_server_dash.py constructed the server for its network mode with the interface restricted to loopback and no transport-security settings, so a name that had been pointed at the loopback address still reached the listener while carrying the attacker's host name. A page in a visitor's browser could therefore drive the local server and invoke its company-search and file-detail tools under the Dropbox credential the server holds. Only the network mode was reachable this way; the standard input mode was not. The fix supplies transport-security settings that enable host checking and allow only the loopback name and port, rejecting other hosts before a tool runs. The repository publishes no versions, so the affected boundary is the commit preceding the fix.

Weakness: CWE-346 (Origin Validation Error)

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


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

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

## Is CVE-2026-81102 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81102 is a low-severity server-side request forgery vulnerability in dropbox mcp-server-dash, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-81102 in the wild and no public exploit code.

Affected product: dropbox mcp-server-dash. 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-81102/ (Markdown: https://insights.sbomify.com/CVE-2026-81102/index.md)
```

## Sources

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

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