CVE-2026-73659: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in triggerdotdev trigger.dev
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.
AI Analysis
Technical Summary
Trigger.dev, an open-source platform for AI workflows in TypeScript, has a path traversal vulnerability (CWE-22) identified as CVE-2026-73659. In versions 4.4.2 through 4.4.x prior to 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. This allows '..' traversal to escape the packets/<projectRef>/<env>/ object-store prefix, enabling a project API key to read or overwrite another organization's offloaded task payloads and outputs on multi-organization self-hosted instances. The issue is resolved in version 4.5.0.
Potential Impact
Exploitation of this vulnerability allows an attacker with a project API key to access or modify data belonging to other organizations hosted on the same self-hosted instance. This compromises confidentiality and integrity of offloaded task payloads and outputs, potentially leading to data leakage or unauthorized data manipulation.
Mitigation Recommendations
Upgrade to Trigger.dev version 4.5.0 or later, where this path traversal vulnerability is fixed. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor advisory indicating the fix in 4.5.0.
CVE-2026-73659: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in triggerdotdev trigger.dev
Description
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.
CVSS v3.1
Score 8.1high
Affected software
pkg:github/triggerdotdev/trigger.devRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Trigger.dev, an open-source platform for AI workflows in TypeScript, has a path traversal vulnerability (CWE-22) identified as CVE-2026-73659. In versions 4.4.2 through 4.4.x prior to 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. This allows '..' traversal to escape the packets/<projectRef>/<env>/ object-store prefix, enabling a project API key to read or overwrite another organization's offloaded task payloads and outputs on multi-organization self-hosted instances. The issue is resolved in version 4.5.0.
Potential Impact
Exploitation of this vulnerability allows an attacker with a project API key to access or modify data belonging to other organizations hosted on the same self-hosted instance. This compromises confidentiality and integrity of offloaded task payloads and outputs, potentially leading to data leakage or unauthorized data manipulation.
Mitigation Recommendations
Upgrade to Trigger.dev version 4.5.0 or later, where this path traversal vulnerability is fixed. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor advisory indicating the fix in 4.5.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-13T14:04:09.605Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e3a17bf8831d539d70445
Added to database: 08/13/2026, 21:41:43 UTC
Last enriched: 08/13/2026, 21:56:32 UTC
Last updated: 08/13/2026, 22:01:13 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.