← All advisories
CVE-2026-76807criticalAgent hijacking2026-11-18

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.

01.

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.

02.

How to check

  1. Check whether you start todoist-mcp-http (not the default stdio entrypoint) and which @doist/todoist-mcp version it runs.
  2. Review your Todoist activity log for tasks or projects you didn't create, complete or delete.
03.

How to fix

  1. Upgrade @doist/todoist-mcp to 10.3.3 or later.
  2. Prefer the stdio transport for local clients. If you need HTTP, put an authenticating proxy in front that checks the Host and Origin headers.
  3. 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
04.

Sources

More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.