CVE-2026-73659 in trigger.dev
Summary
by MITRE • 08/14/2026
Trigger.dev is the open-source platform for building AI workflows in TypeScript. From 4.4.2 until 4.5.0, the packet presign routes in apps/webapp/app/routes/api.v1.packets.$.ts pass a caller-controlled filename through resolveStoreProtocolForPacketPresign to generatePresignedUrl and generatePresignedRequest in apps/webapp/app/v3/objectStore.server.ts, allowing .. traversal to escape the packets/<projectRef>/<env>/ object-store prefix and enabling a project API key to read or overwrite another organization's offloaded task payloads and outputs on multi-organization self-hosted instances. This issue is fixed in version 4.5.0.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 08/14/2026
The vulnerability exists within Trigger.dev's packet presign functionality across versions 4.4.2 through 4.5.0, specifically affecting the web application's API routes that handle packet operations. The flaw stems from improper input validation where a caller-controlled filename parameter is directly passed through the resolveStoreProtocolForPacketPresign function without adequate sanitization or path validation. This allows malicious actors to manipulate the filename parameter to traverse directory structures using directory traversal sequences such as ".." which can escape the intended object store prefix structure of packets/<projectRef>/<env>/. The vulnerability specifically impacts multi-organization self-hosted instances where multiple organizations share the same infrastructure but should maintain isolated data boundaries.
The technical implementation of this vulnerability leverages path traversal mechanisms that bypass the intended access controls for object storage operations. When the generatePresignedUrl and generatePresignedRequest functions receive the unvalidated filename parameter, they process it through the resolveStoreProtocolForPacketPresign function which fails to properly validate or sanitize the input before constructing the final storage path. This creates a scenario where an attacker with a valid project API key can manipulate the filename to access or modify data outside of their designated project boundaries, effectively breaking the isolation between different organizations within the same self-hosted deployment.
The operational impact of this vulnerability is severe for multi-organization deployments as it allows unauthorized data access and modification across organizational boundaries. An attacker could potentially read sensitive task payloads and outputs belonging to other organizations, or worse, overwrite critical data with malicious content. The vulnerability specifically targets the object storage layer where offloaded task payloads and outputs are stored, making it particularly dangerous for environments handling confidential information. This represents a privilege escalation issue where a user with limited project-level access can gain unauthorized access to other organizations' data within the same deployment instance.
The root cause of this vulnerability aligns with CWE-23 Path Traversal and CWE-770 Allocation of Resources Without Limits or Throttling, specifically manifesting as an improper input validation flaw in the object storage handling logic. From an attacker's perspective, this vulnerability maps to ATT&CK technique T1078 Valid Accounts for maintaining access while leveraging the legitimate API key access to perform unauthorized operations. The fix implemented in version 4.5.0 addresses this by introducing proper path validation and sanitization of filename parameters before they are processed through the object storage functions, ensuring that all paths remain within the intended project and environment boundaries.
Organizations using Trigger.dev should immediately upgrade to version 4.5.0 or later to mitigate this vulnerability. Additional mitigations include implementing network-level restrictions on API endpoints, monitoring for unusual access patterns in object storage operations, and conducting thorough security assessments of multi-organization deployments. The fix demonstrates the importance of proper input validation and path sanitization in distributed systems where multiple tenants share infrastructure resources. Security teams should also implement automated scanning for similar path traversal vulnerabilities across their application codebase, particularly in functions that handle file or object storage operations with user-controllable inputs.