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.
CVE-2026-81102
Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-08-27. the CNA's CVSS baseline 3.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.1
- EG Score
- 3.1(high)
- EG Risk
- 14(Track)EG Risk 14/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity31% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 29, 2026
References (3)
Vendor Advisories for CVE-2026-81102(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 11:59 UTCEG score recompute
- 2026-08-29 11:59 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 20:43 UTCEG score recompute
- 2026-08-28 20:43 UTCGHSA enrichment
- 2026-08-28 19:48 UTCEG score recompute
- 2026-08-28 19:48 UTCGHSA enrichment
- 2026-08-27 17:25 UTCEG score recompute
- 2026-08-27 16:47 UTCEG score recompute
- 2026-08-27 16:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-346
Frequently asked(5)
What is CVE-2026-81102?
When was CVE-2026-81102 disclosed?
Is CVE-2026-81102 actively exploited?
What is the CVSS score of CVE-2026-81102?
How do I remediate CVE-2026-81102?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81102
Is Your Infrastructure Affected by CVE-2026-81102?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.