Vulnerability 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 Score
LOW
Related Weaknesses (CWE)
References
- https://github.com/dropbox/mcp-server-dash
- https://github.com/dropbox/mcp-server-dash/pull/12
- https://www.vulncheck.com/advisories/dropbox-dash-mcp-server-dns-rebinding-via-m
FAQ
What is CVE-2026-81102?
CVE-2026-81102 is a vulnerability with a CVSS score of 3.1 (LOW). 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 restric...
How severe is CVE-2026-81102?
CVE-2026-81102 has been rated LOW with a CVSS base score of 3.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-81102?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.