Dropbox Dash MCP Server DNS Rebinding via Missing Host Header Validation (CVE-2026-81102) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-81102

Dropbox Dash MCP Server DNS Rebinding via Missing Host Header Validation

Answer in brief

CVE-2026-81102 records a Unknown severity vulnerability in Dropbox Dash MCP Server DNS Rebinding via Missing Host Header Validation. The current sources do not mark it as known exploited. The current feed maps dropbox/mcp-server-dash (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Aug 27, 2026Source checked Aug 27, 2026First seen by HOL Aug 27, 2026Material review Aug 27, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps dropbox/mcp-server-dash (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
dropbox/mcp-server-dashgeneric	>=0 <84567b74e3c72e42d5e50ee07c56864613f519c2	84567b74e3c72e42d5e50ee07c56864613f519c2

Recommended response

Check inventory. Check lockfiles and deployed manifests for dropbox/mcp-server-dash.
Review the reported fix. Update dropbox/mcp-server-dash to 84567b74e3c72e42d5e50ee07c56864613f519c2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 27, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.