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

published 2026-08-13 2 mo ago modified 2026-09-18 51 d ago also EUVD-2026-58390

cvss: 9.9; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits: 0; none known

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.

Patch / fix

links 3

github.com/triggerdotdev/trigger.dev@34b1a18 commit
github.com/triggerdotdev/trigger.dev#4199 pull request
github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2 release

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 mo ago (2026-08-14)

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.9	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

Affected products

triggerdotdev trigger.dev

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key
CWE-862 Missing Authorization

References

Sources

CVE List CVE-2026-73656
NVD CVE-2026-73656

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary