Trigger.dev: Cross-environment deployment cancel
Affects trigger.devSource GCVE Database
CVSS 5.4 Medium : upgrade to 4.5.6 when convenient.
Data as of 3 Oct 2026, 17:40 UTC
- Patch
- Available – fixed in 4.5.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LWhat to do
Upgrade trigger.dev to 4.5.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtrigger.dev | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability as indicated by the vendor. Users should upgrade to version 4.5.6 or later where the deployment cancel operation is correctly scoped by environment ID. Until patched, avoid using lower-trust environment keys in contexts where they could be abused to cancel production deployments. Review API key permissions and environment isolation policies. Since this affects self-hosted and cloud deployments, self-hosted users must apply the update; cloud users should verify with the vendor if the service has been updated.
Description
Trigger.dev has a vulnerability where the deployment cancel operation is scoped only by project ID and not by environment ID. This allows an API key for a lower-trust environment (e.g., dev) to cancel deployments in higher-trust environments (e.g., production) within the same project. The deployment GET route correctly enforces environment scoping, but the cancel route does not, creating an authorization bypass. This affects both self-hosted and cloud deployments of Trigger.dev prior to version 4.5.6.
References
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-4672-hwv6-gq62 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/pull/4316 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/commit/6997aeb05e27d2db47f9eda01fdc8a17c81a1ae0 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.6 (opens in a new tab)