CVE-2026-81102

Dropbox Dash MCP Server DNS Rebinding via Missing Host Header Validation

Published Aug 27, 2026 CVSS 4.0 · 2.3 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Dash MCP server is bound to the loopback interface but fails to validate the Host header in incoming HTTP requests. This omission allows an attacker to craft a DNS rebinding attack that resolves a domain name to the loopback address. A web page loaded in the victim's browser can then send properly formed requests carrying the attacker's host name to the local server, triggering its company‑search and file‑detail utilities under the Dropbox credentials that the server maintains. Because the server accepts these requests unconditionally, the attacker can effectively read or enumerate the server's data without needing credentials.

Affected Systems

The affected software is Dropbox's MCP server Dash, isolated to the repository code before the fix. No released versions are published, so any deployment compiled from the commit preceding the patch is vulnerable. The flaw impacts only the network mode, not the standard input mode.

Risk and Exploitability

The CVSS score is 2.3, indicating a low overall risk. EPSS data is unavailable and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires that the target runs the vulnerable MCP server in network mode and that the attacker can host a web page causing the victim's browser to issue requests to the loopback interface. The lack of host validation permits an adversary to indirectly invoke privileged server functions, resulting in limited but potentially sensitive data exposure. The remediation path is to apply the official patch that introduces transport‑security settings enforcing host header validation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest commit that adds transport‑security host header validation to the MCP server code.
  • Configure the server to accept connections only from the loopback interface and the default port.
  • Disable or remove the network mode deployment until the patch is available or restrict it to internal use only.

Generated by OpenCVE AI on August 27, 2026 at 18:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Dropbox
Dropbox mcp-server-dash
Vendors & Products Dropbox
Dropbox mcp-server-dash
Type Values Removed Values Added
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.
Title Dropbox Dash MCP Server DNS Rebinding via Missing Host Header Validation
Weaknesses CWE-346
References
Metrics cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 2.3, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 29, 2026, 11:48 AM
Reserved
Aug 26, 2026, 4:00 PM
Status
Deferred
Published
Aug 27, 2026, 5:20 PM
Modified
Sep 24, 2026, 8:43 PM