Skip to main content
VulnerabilityPublished

CVE-2026-76807: Doist todoist-mcp · Origin Validation Error

Affects Doist todoist-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 10.3.3 as a priority.

Data as of 18 Nov 2026, 20:22 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.3
Patch
Available – fixed in 10.3.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Doist todoist-mcp to 10.3.3.

Affected software

ProductAffectedFixed in
Doisttodoist-mcpAffected
  • <10.3.3
Fixed in
  • 10.3.3

AI-suggested

Upgrade todoist-mcp to version 10.3.3 or later, where this origin validation vulnerability is fixed. No additional mitigation is required as the fix addresses the root cause by validating Host and Origin headers and authenticating browser callers.

Description

A critical origin validation vulnerability (CWE-346) exists in the todoist-mcp HTTP server prior to version 10.3.3. The server accepts browser-origin POST requests to /mcp without validating Host and Origin headers or authenticating the caller. This allows a malicious website to exploit DNS rebinding to access the loopback listener and invoke MCP tools using the server-held Todoist API key, exposing account data and enabling task manipulation. The issue is fixed in version 10.3.3.

References

Community reviews

Loading reviews…