CVE-2026-114090: Trigger.dev CLI `trigger dev --mcp` server listens on all interfaces with no auth and acts with your access token
The MCP server started by the Trigger.dev CLI with `trigger dev --mcp` bound to every network interface and exposed its /sse and /messages endpoints with no authentication. Anyone on the same network, another process on the machine, or a web page the developer opened could call its MCP tools (trigger-task, cancel-run, list-runs, get-run, get-run-logs, list-all-tasks), which run with the developer's stored Trigger.dev access token. Affects the CLI from 3.0.0; fixed in 4.5.4.
What it is
startMcpServer in packages/cli-v3/src/dev/mcpServer.ts called app.listen(port) with no host, so Node listened on 0.0.0.0 / ::, and neither route checked a token or the Origin header (CWE-306).
The server was built with the developer's Trigger.dev API token already bound, so any caller that completed the SSE handshake could queue real task runs in the developer's project, cancel runs, and read run payloads and logs.
The report describes two attackers: a same-network host posting a JSON-RPC tools/call to /messages, and a malicious page in the developer's browser that opens an EventSource to localhost and then posts to /messages.
VulnCheck and NVD list cli-v3 >= 3.0.0, < 4.5.4 as affected; GitHub advisory GHSA-pqmg-rq46-vm4m has the technical write-up.
How to check
- In the project, run `npm ls trigger.dev` (or `npx trigger.dev --version`); anything from 3.0.0 up to 4.5.3 is affected.
- If you have used `trigger dev --mcp`, look at your project's run history for runs you didn't start.
How to fix
- Upgrade the Trigger.dev CLI to 4.5.4 or later.
- Don't run `trigger dev --mcp` on untrusted networks with an older CLI; if you did, rotate your Trigger.dev personal access token (trigger.dev login again) and review recent runs and logs.
npm ls trigger.dev
# while trigger dev --mcp is running, check what it listens on:
lsof -iTCP -sTCP:LISTEN -P | grep node Sources
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalCVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)