Skip to content

AAK-MCP-TRIGGERDEV-CVE-2026-114090-001: Trigger.dev CLI 4.0.0 to 4.5.3: trigger dev --mcp serves MCP on every interface with no authentication

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
TriggerDevCliMcpServerNoAuth

What it detects

The Trigger.dev CLI (npm trigger.dev, published from packages/cli-v3 of triggerdotdev/trigger.dev) starts an MCP server when trigger dev runs with --mcp. Before 4.5.4 that server answered /sse and /messages with no token, Origin or host check, and listened on port 3333 (or --mcp-port) with no host argument, so on every interface. Its tools (trigger-task, cancel-run, list-runs, get-run, get-run-logs, list-all-tasks) call Trigger.dev with the developer's stored access token, so a caller on the network, or a web page the developer opens, can start and cancel runs and read run payloads and logs in the developer's project (CVE-2026-114090, CVSS 3.1 7.1, CWE-306, GHSA-pqmg-rq46-vm4m). Checked in the npm tarballs: 3.0.0 and 3.3.17, the newest 3.x release, have no --mcp option; 4.0.0, and every 4.0.0 beta, ships dist/esm/dev/mcpServer.js calling app.listen(options.port, ...), as 4.5.3 does; 4.5.4 removes the option and the server. The advisory names @trigger.dev/cli-v3 from 3.0.0, a name npm does not carry.

How to fix

Upgrade trigger.dev to 4.5.4 or later and pin it. Until then, do not pass --mcp to trigger dev: a firewall keeps other hosts off port 3333 (or the --mcp-port), but not a web page in the developer's own browser. The trigger.dev mcp command, which 4.5.4 keeps, speaks stdio.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-TRIGGERDEV-CVE-2026-114090-001

Limitations

Reports an npm reference to trigger.dev from 4.0.0 below 4.5.4 that states a version: a package.json or lockfile entry, or the package in an MCP config or a package.json script, reporting a range that admits an affected version. latest was 4.8.4 on 2026-11-11 and states no version, so npx trigger.dev@latest dev is not reported. A pre-release reads as its release, so the 4.0.0 betas read as 4.0.0 and the 4.5.0 release candidates as 4.5.0, and both are reported, as both carry the server. Snapshot builds published as 0.0.0-<name>-<date> read as 0.0.0 and are not reported, though some carry the server (0.0.0-re2-20250815162450 does). It reads the version, not whether trigger dev runs with --mcp, so a project that never passes the flag, or that runs only the stdio trigger.dev mcp command, is reported too. @trigger.dev/cli-v3, the name the advisory gives, is not on npm and is not matched. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References

  • CVE: CVE-2026-114090
  • OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
  • OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities)
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication)
  • CSA AI Controls Matrix (AICM): IAM-01, IVS-04, STA-08

All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-TRIGGERDEV-CVE-2026-114090-001.md: the page then shows that text, with the registry reference appended under it.