Vulnerability · Published Aug 27, 2026 · Assigned by VulnCheck

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

Low 3.1

In plain English

A low-severity security flaw in mcp-server-dash from dropbox. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities).

Severity (CVSS 3.1)3.1Low

Exploit odds (30 days)0.2%top 92.0% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

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.

Affected products (as reported)

Vendor	Product	Versions
dropbox	mcp-server-dash	0 – before 84567b74e3c72e42d5e50ee07c56864613f519c2

Weakness: CWE-346 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

References

https://github.com/dropbox/mcp-server-dash product
https://github.com/dropbox/mcp-server-dash/pull/12 issue-tracking, patch
VulnCheck Advisory: Dropbox Dash MCP Server DNS Rebinding via Missing Host Header Validation third-party-advisory