CVE-2026-81099

What it is

tiger-slack started its MCP HTTP transport without enabling the host allow-list the underlying SDK provides. mcp/src/httpServer.ts called the shared httpServerFactory helper and never set the DNS-rebinding-protection option, so the transport accepted a request whatever host it named, and a page in a browser could point a name it controlled at the address the server was bound to and drive the locally reachable Slack MCP server through the visitor's browser. The fix passes the option explicitly alongside a dependency update; the update alone would not have closed it. The repository publishes no release that brackets the fix, so the affected boundary is the commit preceding it.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-27 17:20 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-23 17:17 UTC Last updatedMost recent change to the record

Details

Published

2026-08-27 17:20 UTC

Last modified

2026-09-23 17:17 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-346

Record status

Deferred

Attack profile CVSS 4.0 · 7.6

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

Passive

Confidentiality

High

Integrity

High

Availability

None