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.