Skip to main content
Menu
CVEs

CVE

Doist Todoist MCP origin validation bypass in local HTTP server

Affects the optional todoist-mcp-http Streamable HTTP server in Doist's todoist-mcp only while that server is running. Fixed in 10.3.3.

CVE-2026-76807EUVD-2026-129178Published Updated Summary written by a model

9.3CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 10.3.3
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. The optional todoist-mcp-http Streamable HTTP server is running.

Summary

Doist's Todoist MCP Server has a flaw in its HTTP server that lets a malicious website, visited in a browser, reach the server running on the local machine without logging in. An attacker who gets a user to visit that site can read Todoist account data and create, update, complete, or delete tasks using the server's stored Todoist API key.

Original description

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.

Who should check

Teams running Doist todoist-mcp's optional todoist-mcp-http Streamable HTTP server, including local setups that bind to 127.0.0.1 with a TODOIST_API_KEY.

“The self-hosted todoist-mcp-http server accepts browser-origin MCP requests”

github.com

cve.now Index

37Pcve.now Index 37 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    The optional todoist-mcp-http Streamable HTTP server is running.
  • Upgrade to a fixed version: 10.3.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-76807 (Todoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-76807 (entry last updated 2026-11-18):
Affected:
- Doist todoist-mcp: fixed in 10.3.3
Fixed versions: 10.3.3.
Conditions (all must be true for the bug to be hit):
- The optional todoist-mcp-http Streamable HTTP server is running. (source: https://github.com/todoist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-76807 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76807 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/todoist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h
- https://github.com/todoist/todoist-mcp/pull/516
- https://github.com/todoist/todoist-mcp/commit/245bf29cf5dbd8272e2aa896ad38557f91f8a16a
- https://github.com/todoist/todoist-mcp/releases/tag/v10.3.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-76807
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76807"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  5. Record last updated

Affected versions

  • Doist todoist-mcp

    fixed in 10.3.3

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · todoist/todoist-mcp · Advisory GHSA-833v-v58w-294h
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-76807
RecordNVD · CVE-2026-76807
Other links 3
RepositoryGitHub · todoist/todoist-mcp · Pull request #516
RepositoryGitHub · todoist/todoist-mcp · Commit 245bf29c
RepositoryGitHub · todoist/todoist-mcp · Release v10.3.3

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-76807

Is CVE-2026-76807 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A malicious website can use DNS rebinding to call Todoist MCP tools on a local server, using the operator's Todoist API key. This can read account data and create, complete, update or delete Todoist items.Source: github.com

Which versions are affected by CVE-2026-76807?

todoist-mcp: before 10.3.3.Source: cve.now feed data

Am I affected, and how do I check?

Versions of todoist-mcp before 10.3.3 are affected, but only when the optional todoist-mcp-http Streamable HTTP server is running. Check the installed todoist-mcp version and whether that HTTP server is started.Source: github.com

How do I fix CVE-2026-76807?

Upgrade todoist-mcp to 10.3.3 or later.Source: github.com

More CVEs