CVE-2026-85651: Trigger.dev Cross-Tenant Write Vulnerability in Task Replay Functionality
Summary
CVE-2026-85651: Trigger.dev: Run replay injects a task run into an attacker-chosen environment (cross-tenant write). Affects trigger.dev versions < 4.5.2. Fixed in 4.5.2. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Trigger.dev is a platform that allows developers to automate workflows and manage task executions across different environments. It provides a user-friendly dashboard for monitoring task runs and replaying them as needed. However, a significant vulnerability has been identified in its replay functionality, which allows authenticated users to execute task runs in environments belonging to other organizations, leading to unauthorized access and potential data pollution.
Vulnerability Detail
The vulnerability arises from the way Trigger.dev handles the replay action for task runs. While the source run is correctly authorized to belong to the caller's organization, the target environment for the replay is directly taken from the user's input without any validation for organizational or project membership. This oversight allows an authenticated user to replay their own task runs into environments of other organizations, consuming resources and polluting the run history of the victim organization. The lack of checks in the environment lookup process means that an attacker can exploit this vulnerability to create unauthorized task runs in another tenant's environment, potentially affecting production systems.
How To Fix
Latest published version: 4.7.7 as of 22 Oct 2026
npm install trigger.dev@4.7.7Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
4.5.2
This is the first release that contains the fix.
npm install trigger.dev@4.5.2Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, ensure that users are restricted from accessing environment IDs that do not belong to their organization. Implement additional checks in the replay action to validate the environment ID against the user's organization and project membership.
Conclusion
The CVE-2026-85651 vulnerability in Trigger.dev poses a significant risk by allowing authenticated users to execute task runs in unauthorized environments. It is crucial to update to the patched version 4.5.2 to secure your application and prevent potential exploitation.
See every vulnerability recorded for trigger.dev →
FAQ
CVE-2026-85651 is a vulnerability in Trigger.dev that allows authenticated users to replay task runs into environments belonging to other organizations, leading to unauthorized access and resource consumption.
You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signing up.
The vulnerability can lead to unauthorized task runs in another tenant's environment, consuming their resources and polluting their run history, which could disrupt operations.
Yes, a patch is available in version 4.5.2 of the Trigger.dev package. It is recommended to update to this version to mitigate the vulnerability.
The CVSS score of this vulnerability is 7.1, indicating a high severity level.
References
Related vulnerabilities
Recent vulnerabilities recorded for trigger.dev.
