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.
{
"cna_assigner": "VulnCheck",
"cwe_ids": [
"CWE-346"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/81xxx/CVE-2026-81099.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "23faf7ee7e7f73e5ea4f67e627c1aca94bba1f09"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}