Security Digest · Vulnerability record
CVE-2026-76807: Todoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server
Todoist MCP Server provides tools that allow AI agents to access and modify a Todoist account.
CVSS 9.3 Critical EPSS 0.2% · p12
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.2%, percentile 12: FIRST’s model estimates a 0.2% chance of exploitation activity in the next 30 days, higher than 12% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Needs a user to click or open something. Phishing makes that realistic, but it is not wormable.
- Only applies if your dependency tree includes
@doist/todoist-mcp(npm) <= 10.3.2, fixed in 10.3.3. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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 a victim's local 127.0.0.1 MCP server, then invoke Todoist MCP tools without a caller credential.
This affects github.com/Doist/todoist-mcp at commit d2903e0d945d2a559d71c091337ad6380511e62f, package version 10.3.1, when the optional Streamable HTTP server is running. The stdio entrypoint is not browser-reachable. The vulnerable browser-reachable component is todoist-mcp-http.
The documented HTTP server mode runs all MCP tools with the operator's TODOISTAPIKEY and binds to loopback by default:
src/main-http.ts:28-30 sets the HTTP bind host and port:
src/main-http.ts:88-99 dispatches POST /mcp to StreamableHTTPServerTransport without validating Host or Origin:
Weakness type: CWE-346, CWE-350.
Product: @doist/todoist-mcp (npm) · Assigned by: GitHub_M · Published: 2026-11-18
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| npm | @doist/todoist-mcp | <= 10.3.2 | 10.3.3 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Doist | todoist-mcp | < 10.3.3 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 3.1 | 9.3 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N |
| GitHub | 3.1 | 9.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: required (a user must click/open something)
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
- FIRST EPSS (model of 2026-11-21): 0.22% probability of exploitation activity in the next 30 days; percentile 12.
Timeline
- — CVE record last updated
- — CVE record published by GitHub_M
- — GitHub-reviewed advisory GHSA-833v-v58w-294h published (critical)
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-833v-v58w-294h github.com
- CVE.org record CVE-2026-76807 cve.org
- NVD entry CVE-2026-76807 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com