CVE & CISA-KEV Catalog

CVE-2026-81102

LOW
3.1
CVSS v3
NVD

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged

Impact

ConfidentialityLow
IntegrityNone
AvailabilityNone

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Exploit Intelligence

0.14%probability of exploitation in 30 days
4thpercentile

Low risk: more likely to be exploited than 4% of all known CVEs.

References

Related Vulnerabilities

Other CWE-346 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2025-34291High8.884%KEV-
CVE-2009-1185High7.282%-Fix
CVE-2015-4495High8.871%KEVFix
CVE-2020-16952High8.671%--
CVE-2023-29711Critical9.870%--
CVE-2024-23898High8.867%-Fix

Common questions

How do I fix CVE-2026-81102?

No published fix for CVE-2026-81102 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-81102 being actively exploited?

Not that we know of. CVE-2026-81102 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.14% is the estimated probability that it will be exploited in the next 30 days. That is higher than 4% of all scored CVEs.

How severe is CVE-2026-81102?

CVE-2026-81102 has a CVSS v3 base score of 3.1, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-81102
CVE-2026-81102 severity badge

Markdown

[![CVE-2026-81102](https://tridentstack.com/cve/badge/CVE-2026-81102.svg)](https://tridentstack.com/cve/CVE-2026-81102)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-81102"><img src="https://tridentstack.com/cve/badge/CVE-2026-81102.svg" alt="CVE-2026-81102"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.