CVE-2026-76807

waiting for further signalsZero needs more public information before it can validate it.

GHSA-833v-v58w-294h ↗EUVD-2026-129178 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Doist todoist-mcp <= 10.3.2
fixed in 10.3.3
CWE-346 Origin Validation Error
ETK-2026-4889Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/@doist/todoist-mcp
10h 55msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+10h59m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

todoist-mcp versions before 10.3.3 are affected when the optional HTTP server is enabled. A malicious website may use DNS rebinding to access the local service and perform Todoist account actions with the server's configured API credential; the browser must be able to reach the loopback listener.

mitigation

Upgrade todoist-mcp to version 10.3.3 or later. Until upgrading, disable the optional HTTP server and use the stdio transport where practical.

fixed in 10.3.3

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 20:08Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-18 20:08Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-76807

{
  "etk_id": "ETK-2026-4889",
  "cve_id": "CVE-2026-76807",
  "display_id": "CVE-2026-76807",
  "ghsa_id": "GHSA-833v-v58w-294h",
  "euvd_id": "EUVD-2026-129178",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Origin validation flaw in todoist-mcp HTTP server",
  "summary": "todoist-mcp versions before 10.3.3 are affected when the optional HTTP server is enabled. A malicious website may use DNS rebinding to access the local service and perform Todoist account actions with the server's configured API credential; the browser must be able to reach the loopback listener.",
  "mitigation": "Upgrade todoist-mcp to version 10.3.3 or later. Until upgrading, disable the optional HTTP server and use the stdio transport where practical.",
  "vendor": "Doist",
  "product": "todoist-mcp",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 10.3.2"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "10.3.3"
      ],
      "package_name": "@doist/todoist-mcp",
      "purl": "pkg:npm/@doist/todoist-mcp"
    }
  ],
  "cwes": [
    346
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.228132366666667,
  "t0_at": "2026-11-18T20:08:01.712000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T20:08:01.712000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T20:08:01.712000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76807"
    }
  }
}

published 2026-11-19 06:36Z
last change 2026-11-19 16:49Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.