Threat Intelligence Database

Trigger.dev versions from 4.4.2 up to but not including 4.5.0 contain a path traversal vulnerability in the packet presign routes. This flaw allows a caller-controlled filename to escape the intended restricted directory, enabling unauthorized read or overwrite access to other organizations' offloaded task payloads and outputs in multi-organization self-hosted instances. The vulnerability is fixed in version 4.5.0.

CVE-2026-73658 is a high-severity vulnerability in trigger.dev, a platform for building and deploying AI agents and workflows. Versions from 4.4.2 up to but not including 4.5.0-rc.5 contain improper input validation in the Aws4FetchClient component, allowing user-controlled packet keys to be assigned to URL pathnames without proper normalization and ownership checks. This flaw enables an attacker with a valid environment API key to obtain presigned URLs for other tenants' object-store keys, potentially reading or overwriting task payloads. The issue is fixed starting from version 4.5.0-rc.5. The vulnerability has a CVSS score of 8.2, indicating high impact on confidentiality and integrity but no impact on availability.

Trigger.dev versions from 4.4.2 up to but not including 4.5.0-rc.4 contain a path traversal vulnerability and improper access control in the replay API endpoint. This allows any valid environment API key to replay another tenant's run by friendlyId, potentially consuming victim resources and repeating side effects. Additionally, when using a specific payload type, an attacker can overwrite payload bytes via a separate object-store path traversal, injecting attacker-controlled input into the victim's task. The issue is fixed starting with version 4.5.0-rc.4.

Trigger.dev versions prior to 4.5.6 contain an authorization bypass vulnerability in the background worker deployment API. The flaw allows a user with a valid API key for one project to manipulate another project's deployment by linking an attacker-owned background worker to the victim deployment and changing its state from BUILDING to DEPLOYING. This issue is addressed in version 4.5.6.

Trigger.dev versions prior to 4.5.2 contain an improper authentication vulnerability in the Google authentication flow. The vulnerability allows an attacker to link an unverified Google email profile to an existing account with the same email, potentially taking over that account. This issue is resolved in version 4.5.2.

Trigger.dev versions prior to 4.5.6 contain a prototype pollution vulnerability in the PUT /api/v1/runs/:runId/metadata endpoint. This flaw allows an attacker with a normal environment API key to modify Object.prototype in the shared webapp process, leading to corruption of Prisma queries and Prometheus labels, breaking worker authentication for other tenants, and causing a process-wide denial of service. The issue is fixed in version 4.5.6.