Timescale tiger-slack DNS Rebinding via Disabled Host Header Allow-List
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 23faf7ee7e7f73e5ea4f67e627c1aca94bba1f09.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| timescale | <23faf7ee7e7f73e5ea4f67e627c1aca94bba1f09 | 23faf7ee7e7f73e5ea4f67e627c1aca94bba1f09 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket