CVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)
The optional todoist-mcp-http server in @doist/todoist-mcp (Doist's official Todoist MCP server) runs every MCP tool with the operator's TODOIST_API_KEY and listens on 127.0.0.1:3000 by default, but up to 10.3.2 it accepted POST /mcp from any browser origin without checking the Host or Origin header or authenticating the caller. A malicious web page can use DNS rebinding to reach that loopback listener and call the Todoist tools: read the account, and create, update, complete or delete tasks and other objects. The stdio transport is not browser-reachable and is not affected. Fixed in 10.3.3.
What it is
src/main-http.ts dispatches POST /mcp straight to StreamableHTTPServerTransport. The requireValidTodoistToken middleware only checks that the server's own Todoist token is valid; it never authenticates the browser caller (CWE-346 / CWE-350).
The advisory's proof of concept rebinds an attacker origin to 127.0.0.1, lists the tools, calls user-info to get the account behind the server-held key and calls add-tasks to create a task. Registered tools include add-tasks, complete-tasks, update-tasks, delete-object, comments, reminders, labels, filters, goals and assignments.
Affected: @doist/todoist-mcp <= 10.3.2 when you run the todoist-mcp-http entrypoint (for example npx -p @doist/todoist-mcp todoist-mcp-http). Version 10.3.3 was released on 24 June 2026; the CVE was published on 18 November 2026.
How to check
- Check whether you start todoist-mcp-http (not the default stdio entrypoint) and which @doist/todoist-mcp version it runs.
- Review your Todoist activity log for tasks or projects you didn't create, complete or delete.
How to fix
- Upgrade @doist/todoist-mcp to 10.3.3 or later.
- Prefer the stdio transport for local clients. If you need HTTP, put an authenticating proxy in front that checks the Host and Origin headers.
- If an affected HTTP server ran while you were browsing, consider rotating the Todoist API token it used.
npm ls @doist/todoist-mcp
npm ls -g @doist/todoist-mcp Sources
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalMalicious AI agent and MCP packages: mcp-aevo-server (PyPI) steals Aevo trading keys and wallet private keys; vamp-mcp, tsc-ai and @tnhorg/agent-skills (npm) flagged as malware