Trigger.dev, an open-source platform for building AI workflows in TypeScript, has a CWE-22 path traversal vulnerability (CVE-2026-73659) affecting versions >=4.4.2 and <4.5.0. The issue arises because the packet presign routes pass a caller-controlled filename through resolveStoreProtocolForPacketPresign to generatePresignedUrl and generatePresignedRequest, allowing directory traversal sequences ('..') to escape the packets/<projectRef>/<env>/ object-store prefix. This enables a project API key to access or modify another organization's offloaded task payloads and outputs on multi-organization self-hosted instances. The vulnerability is resolved in version 4.5.0.

An attacker with a project API key can exploit this vulnerability to read or overwrite task payloads and outputs belonging to other organizations within the same multi-organization self-hosted instance. This results in unauthorized data access and potential data tampering. The vulnerability does not affect availability but has high confidentiality and integrity impact.

Upgrade to trigger.dev version 4.5.0 or later, where this path traversal vulnerability is fixed. Since this is a self-hosted product, users must apply the update themselves. Patch status is confirmed by the vendor stating the issue is fixed in 4.5.0.