Summary
The optional todoist-mcp-http server accepts browser-originated requests without validating the Host and Origin headers, allowing a malicious website to use DNS rebinding to invoke Todoist MCP tools. It affects @doist/todoist-mcp up to version 10.3.2; the vendor fixed it in 10.3.3.
What happened
The self-hosted todoist-mcp-http server accepts browser-origin MCP requests with attacker-controlled Host and Origin headers. A malicious website can use DNS rebinding to route its own origin to the victim's local MCP server (127.0.0.1) and invoke Todoist MCP tools without any caller credential. The server runs all tools with the operator's Todoist API key, and the existing validation only checks that server-side token; it does not authenticate the browser caller. The exposed tools include read and write operations on tasks, comments, reminders, labels, filters, goals and assignments, including creating, updating, completing and deleting. According to the source, the issue occurs when the optional Streamable HTTP server is running; the stdio entrypoint is not reachable from a browser. The source classifies it as CWE-346 and CWE-350.
Why it matters
While the HTTP server is running, a web page visited by the user could read and modify data in the Todoist account tied to the operator's API key. The source assigns a CVSS 3.1 score of 9.3 (critical severity; vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N) and requires user interaction. CISA's KEV catalog does not list it as actively exploited, and the source does not state that it is a zero-day.
Affected products and versions
@doist/todoist-mcp (npm), versions <= 10.3.2. The source mentions package version 10.3.1 and the optional todoist-mcp-http component. Fixed version: 10.3.3.
| Product | Versions | Fixed in |
|---|---|---|
| @doist/todoist-mcp | <= 10.3.2 | 10.3.3 |
| Doist todoist-mcp | < 10.3.3 | — |
Action recommended by the source
The source states the issue is fixed in @doist/todoist-mcp version 10.3.3. Vendor references include the v10.3.3 release, pull request 516 and a fix commit in the todoist/todoist-mcp repository. The source does not state any other mitigations.
Fixed in: 10.3.3
Sources and references
- https://github.com/advisories/GHSA-833v-v58w-294h — GHSA
- https://github.com/Doist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h — GHSA
- https://github.com/todoist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h — GHSA
- https://nvd.nist.gov/vuln/detail/CVE-2026-76807 — GHSA
- https://github.com/todoist/todoist-mcp/pull/516 — GHSA
- https://github.com/todoist/todoist-mcp/commit/245bf29cf5dbd8272e2aa896ad38557f91f8a16a — GHSA
- https://github.com/todoist/todoist-mcp/releases/tag/v10.3.3 — GHSA
Weaknesses (CWE): CWE-346, CWE-350
Relevant change history
Published
Advisory published.