cve.bz

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

9.3 criticalEPSS 0.2%Fix available

Critical (9.3) in doist todoist-mcp. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @doist/todoist-mcp 10.3.3.

On this page
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.

Severity

CVSS 3.1

9.3 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-11-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-346 Origin Validation Error
CWE-350 Reliance on Reverse DNS Resolution for a Security-Critical Action
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @doist/todoist-mcp (npm): fixed in 10.3.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-76807 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-76807?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-76807?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-76807 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Doist todoist-mcp< 10.3.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-833v-v58w-294hnpm@doist/todoist-mcp<10.3.310.3.3

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-89 Pharming Likelihood: High · Severity: Very High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-275 DNS Rebinding Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-346 (16).

References

Check your stackJSON