CVE-2026-76807

A web page could control a local Todoist MCP HTTP server

Doist · todoist-mcp

First documented disclosure · Review checkpoint

Summary

DNS rebinding could let a visited page use the server-held Todoist credential.

Severity and exploitation evidence

Critical · 9.3/10 · CVSS 3.1. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed originals. A demonstration or absence from KEV does not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The optional HTTP listener did not validate Host or Origin or authenticate browser callers.

Conditions required

The operator runs todoist-mcp-http and visits attacker-controlled content. The stdio transport is unaffected.

Potential impact

Todoist data can be read and tasks created, changed, completed or deleted with the configured account's authority.

Affected versions and configurations

todoist-mcp: < 10.3.3.

Fix and mitigation status

10.3.3.

Practical next steps

Apply the issue-specific correction: 10.3.3. Restrict the affected tool or endpoint until the correction is deployed.

Operating lesson

Loopback binding requires browser-origin and host protections as well as authentication.

Evidence and limits

Earliest reviewed public evidence 2026-06-24; CVE publication 2026-11-18. CVSS 3.1 9.3 is attributed to GitHub_M in the CNA record.

Sources