EM-20261119-XH05
VulnerabilityCritical severity
Critical Todoist MCP Server Vulnerability (CVE-2026-76807)
CVE-2026-76807
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 18 20:19 UTCC6 NVD CVE API 2.0
- Page Born
- Nov 19 20:38 UTCsecond source joined
- Last Signal
- Nov 19 20:38 UTC10 hours before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 29 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 18 20:19 UTCC6 NVD published
- Scored: reachedNov 18 20:19 UTCCVSS 9.3 · EPSS 0.2%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-833v-v58w-294h / CVE-2026-76807: Todoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server (opens source in a new tab) npm:@doist/todoist-mcp Crit severityDatabaseC26 GitHub Advisory Database
- CVE-2026-76807 (CVSS 9.3) (opens source in a new tab) 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… Crit severityDatabaseC6 NVD CVE API 2.0