Trigger.dev before 4.5.12 contains an authorization bypass that lets holders of capability‑restricted user‑actor tokens create alert channels using the legacy personal access token helper. An attacker with a read‑only UAT can POST to the project alertChannels API to add production webhook channels, directing future deployment and error alerts to infrastructure they control. This allows the attacker to receive sensitive operational information and potentially exfiltrate or manipulate alert payloads.

The affected product is Trigger.dev, version 4.5.12 or earlier. Only deployments utilizing Trigger.dev prior to the 4.5.12 release are impacted. Systems that use the legacy personal access token helper are also vulnerable.

The CVSS score of 5.3 indicates a moderate severity, while the EPSS score of less than 1 % suggests a low probability of exploitation at this time. The vulnerability is not listed in the CISA KEV catalog. Attackers would need a valid capability‑restricted user‑actor token with read‑only access; with that token, they can send POST requests to the alertChannels endpoint to create unauthorized alert channels. The API gateway and network perimeter can thus be leveraged to inject malicious webhook endpoints.