CVE-2026-73659

Received Received - Intake

Path Traversal in Trigger.dev

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-13

Last Modified

2026-08-13

Generated

2026-08-14

AI Q&A

2026-08-14

EPSS Evaluated

N/A

NVD

CVE-2026-73659

Affected Vendors & Products

Vendor	Product	Version / Range
trigger.dev	trigger.dev	From 4.4.2 (inc) to 4.5.0 (inc)
trigger.dev	trigger.dev	4.5.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-22	The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

Executive Summary

This vulnerability affects Trigger.dev versions 4.4.2 to 4.5.0. It involves a path traversal issue in the packet presign routes where a caller-controlled filename is passed through a function that generates a presigned URL. This allows an attacker to escape the intended object-store prefix and access or modify another organization's task payloads and outputs on multi-organization self-hosted instances using a project API key.

Detection Guidance

This vulnerability affects Trigger.dev versions 4.4.2 to 4.5.0. To detect it, check the installed version of Trigger.dev using commands like npm list trigger.dev or checking package.json. Verify if any custom API routes or configurations allow packet presign operations with user-controlled filenames.

Impact Analysis

If you are using a vulnerable version of Trigger.dev in a multi-organization self-hosted setup, an attacker with a project API key could read or overwrite another organization's offloaded task data. This could lead to data leaks, unauthorized modifications, or service disruption for affected organizations.

Compliance Impact

This vulnerability could lead to unauthorized access or modification of sensitive data, which may violate compliance requirements under GDPR, HIPAA, or other regulations. It risks exposing personal or health data to unauthorized parties, potentially resulting in legal penalties and reputational damage.

Mitigation Strategies

Upgrade Trigger.dev to version 4.5.0 or later immediately. Review and restrict API key permissions, especially for multi-organization instances. Audit packet presign routes to ensure filename parameters are properly validated and cannot traverse directories.

Hi! I’m here to help you understand CVE-2026-73659. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70