Trigger.dev before version 4.5.2 is vulnerable to a blind server‑side request forgery. An authenticated project member can set an arbitrary webhook URL in an alert channel without validation. Triggering an alert causes the server to send a request to that URL, which can point to internal or cloud metadata services and the attacker can probe internal network reachability and send signed POST requests. The flaw is classified as CWE‑918 and can lead to internal data exposure or further exploitation through internal services.

The vulnerability affects the triggerdotdev:trigger.dev application, versions earlier than 4.5.2. Any deployment using Trigger.dev 4.5.1 or older is at risk. The specific version range is not detailed but includes all releases before the 4.5.2 patch.

The CVSS score is 5.3, indicating a moderate impact. The EPSS score is below 1%, suggesting a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Attackers must be authenticated project members; the vector relies on the server following an unauthenticated webhook call. Although the exploitation window is limited, an attacker who can create alert channels can probe internal resources, send arbitrary signed POST requests, and potentially gain further access. The overall risk is moderate but actionable, recommending immediate patching.