CVE-2026-76807

GHSA-833v-v58w-294h · published 18 Nov 2026 · updated 19 Nov 2026

Todoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server

9.3CriticalCVSS 9.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in @doist/todoist-mcp 10.3.3.

Todoist MCP Server provides tools that allow AI agents to access and modify a Todoist account. Prior to 10.3.3, the optional todoist-mcp-http server accepts browser-origin requests to POST /mcp without validating the Host and Origin headers or authenticating the browser caller. A malicious website can use DNS rebinding to reach the loopback listener and invoke MCP tools through StreamableHTTPServerTransport, which uses the server-held Todoist API key. This exposes Todoist account data and permits operations such as task creation, updates, completion, and deletion. The stdio transport is not browser-reachable and is not affected by this attack path. This issue is fixed in version 10.3.3.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
doist<10.3.3
npm: @doist/todoist-mcp<10.3.3, <=10.3.210.3.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-76807 severity on Zeptric[![CVE-2026-76807](https://zeptric.io/badge/cve/CVE-2026-76807.svg)](https://zeptric.io/cve/CVE-2026-76807)