CVE-2026-81102
Received Received - Intake

Dash MCP Server Loopback Bypass Leading to Credential Exposure

Publication date: 2026-08-27

Last updated on: 2026-08-27

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-27
Last Modified
2026-08-27
Generated
2026-08-27
AI Q&A
2026-08-27
EPSS Evaluated
N/A
NVD
CVE-2026-81102
EUVD
EUVD-2026-67030

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
dropbox dash_mcp_server to 84567b74e3c72e42d5e50ee07c56864613f519c2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-81102 is a DNS rebinding vulnerability in the Dropbox Dash MCP Server. The server binds its listener to the loopback address but fails to validate the host header in incoming requests. This allows an attacker to manipulate the host header so that requests with an attacker-controlled hostname still reach the server. The vulnerability only affects the network mode, not the standard input mode.

Detection Guidance

Check if the Dropbox Dash MCP server is running in network mode bound to 127.0.0.1 without host header validation. Inspect server logs for requests with non-loopback host headers reaching the loopback-bound listener. Use network monitoring tools to detect unexpected local server interactions from browser pages.

Impact Analysis

An attacker could exploit this to interact with the server's tools, such as company-search and file-detail, using the Dropbox credentials the server holds. A malicious webpage in a victim's browser could drive the local server and invoke these tools, potentially accessing sensitive data or performing unauthorized actions.

Mitigation Strategies

Update to the fixed commit 84567b74e3c72e42d5e50ee07c56864613f519c2 or later. Ensure TransportSecuritySettings are enabled to enforce host checking and restrict access to loopback only. Disable network mode if unused and audit OAuth token storage for plaintext exposure.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-81102. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart