AI Stack Alert High CVE-2026-76807 For AppSec, AI Eng, SOC / IR AI-assisted
CVE-2026-76807: Todoist MCP Server HTTP transport lacks Host/Origin checks, enabling DNS rebinding access
The optional todoist-mcp-http server in Todoist MCP Server prior to 10.3.3 accepts browser-origin POST requests to /mcp without validating Host and Origin headers or authenticating the caller. A malicious website can use DNS rebinding to reach the loopback listener and invoke MCP tools that use the server-held Todoist API key. The issue is fixed in version 10.3.3, and the stdio transport is not affected.
Why it matters
Any user running the HTTP server can have Todoist account data read and tasks created, updated, completed, or deleted by a website they visit. The attacker does not need the API key, since the server supplies it.
Do this
- Upgrade Todoist MCP Server to version 10.3.3 or later.
- Until patched, stop running the todoist-mcp-http server or restrict it so it is not reachable from browsers.
- Prefer the stdio transport, which the source states is not browser-reachable and not affected.
- Review Todoist account activity for unexpected task creation, modification, or deletion on hosts that ran the HTTP server.
- Rotate the Todoist API key used by affected servers after patching if unauthorized activity is suspected.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 9.3CVSS
- NoPublic PoC
- 36/100Priority
- 80%Confidence
Evidence
“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 issue is fixed in version 10.3.3.”
Sources
Affected / related
Todoist MCP Server, todoist-mcp-http, DNS rebinding
Published 2026-11-18 20:19 UTC · updated 2026-11-18 22:35 UTC · AI-assisted summary, checked against quoted sources · How we score