Trigger.dev versions 4.4.2 through 4.5.0-rc.5 contain an improper input validation vulnerability in Aws4FetchClient.buildUrl() and Aws4FetchClient.presign() where user-controlled packet keys are assigned directly to URL.pathname without rejecting dot segments. The API endpoint accepts parameters without rejecting path traversal sequences, and the resource lookup lacks per-resource ownership validation. Due to WHATWG path normalization collapsing '..' segments before signing, an attacker with a valid environment API key can craft requests to obtain presigned URLs for other tenants' object-store keys, enabling unauthorized read or overwrite of task payloads. This vulnerability is resolved in version 4.5.0-rc.5.

An attacker with a valid environment API key can exploit this vulnerability to access or modify object-store keys belonging to other tenants, leading to unauthorized disclosure and alteration of task payloads. This compromises confidentiality and integrity of data across tenants within the trigger.dev platform. Availability is not impacted.

The vendor manages remediation for this cloud-hosted service. The vulnerability is fixed in version 4.5.0-rc.5. Users should ensure they are using this version or later to prevent exploitation. Patch status is confirmed as available. No additional mitigation steps are indicated by the vendor advisory.