Timescale tiger-slack
Timescale tiger-slack DNS Rebinding via Disabled Host Header Allow-List
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 23faf7ee7e7f73e5ea4f67e627c1aca94bba1f09
Fixed in 23faf7ee7e7f73e5ea4f67e627c1aca94bba1f09
Mitigation
Upgrade tiger-slack to 23faf7ee7e7f73e5ea4f67e627c1aca94bba1f09 or later.
References
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.