DNS rebinding in @doist/todoist-mcp HTTP server lets websites drive Todoist tools (CVE-2026-76807)
Severity: critical · Patch status: patched · Since 2026-11-19 · CVE-2026-76807
The optional Streamable HTTP entrypoint (todoist-mcp-http) of the @doist/todoist-mcp npm package binds to 127.0.0.1 by default but does not validate Host or Origin headers on POST /mcp, and its token middleware only validates the server-side TODOISTAPIKEY without authenticating the browser caller. A malicious website can use DNS rebinding to route its origin to a victim's loopback server and invoke all registered MCP tools—task creation, completion, updates, deletion, comments, reminders, labels, filters, goals—using the operator's API key. Published PoC shows account enumeration and task write/complete. All versions <=10.3.2 are affected when the HTTP transport is running; the stdio entrypoint is not browser-reachable. Fixed in 10.3.3.
What to do
- Upgrade @doist/todoist-mcp to 10.3.3 or later
- Stop running todoist-mcp-http until patched, or bind behind a proxy that validates Host/Origin
- Avoid exposing the HTTP transport beyond loopback; prefer the stdio entrypoint
- Rotate the TODOIST_API_KEY if the HTTP server was reachable while browsing untrusted sites
Fixed versions
- @doist/todoist-mcp 10.3.3
Sources
All live incidents on Threat Watch