by Kastro
Paper/Archive/CVE-2026-73656

CVE-2026-73656

triggerdotdev trigger.dev — Trigger.dev: Cross-project deployment worker registration can modify another project's deployment state

EPSS 0.5%CVSS 9.9
critical.is priorityof 100
38
CVSS 9.9 (CNA)9.9 / 10 × 3029.7Not in CISA KEV+300.0EPSS percentile 42.6.426 × 208.5No public exploit+100.0SSVC exploitation: none+100.0
Description · from the CVE record

Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. Prior to 4.5.6, POST /api/v1/deployments/:deploymentId/background-workers calls CreateDeploymentBackgroundWorkerServiceV4.call() in apps/webapp/app/v3/services/createDeploymentBackgroundWorkerV4.server.ts, where workerDeployment.findFirst() selects a deployment by friendlyId without an environmentId predicate. A caller with a valid API key for one project can submit another project's deployment identifier, link an attacker-owned background worker to the victim deployment, and move the victim deployment from BUILDING to DEPLOYING. This issue is fixed in version 4.5.6.

Affected

ProductAffectedFixed inSource
trigger.dev< 4.5.2–CNA

Scores by source

GitHub_M (CNA)9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
CISA ADPSSVCExploitation: none · Automatable: no · Technical impact: partial

References

refgithub.com/triggerdotdev/trigger.dev/security/advisories/GHSA-j6vv-pq9h-f4wjrefgithub.com/triggerdotdev/trigger.dev/pull/4199refgithub.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254refgithub.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2