Executive brief
Trigger.dev is an open-source platform for building AI workflows in TypeScript. A path traversal vulnerability in the packet presign API allows a project API key to escape the intended storage directory and read or overwrite task payloads and outputs belonging to other organizations on multi-organization self-hosted instances. This could lead to unauthorized data access, manipulation of workflow data, or disruption of other organizations' operations.
Technical details
The vulnerability is a path traversal flaw in the packet presign routes (apps/webapp/app/routes/api.v1.packets.$.ts) that passes a caller-controlled filename through resolveStoreProtocolForPacketPresign to generatePresignedUrl and generatePresignedRequest without proper validation. An attacker with a project API key can craft paths containing ".." traversal segments to escape the intended packets/<projectRef>/<env>/ object-store prefix and access resources outside their project's scope. The flaw affects versions 4.4.2 through 4.5.0 and is remedied by strict path validation that rejects traversal segments, leading slashes, backslashes, and empty segments before key construction. The fix returns a 400 Bad Request status with a clear error message for invalid paths, preventing the vulnerability regardless of underlying storage backend configuration.
Affected products
- Trigger.dev Trigger.dev 4.4.2 to 4.5.0
Timeline
- 2026-08-13: disclosed
- 2026-06-05: patched: Fix merged in version 4.5.0