Trigger.dev missing authentication in run replay action

Severity: high · CVSS 7.1 · Published 2026-10-02

Trigger.dev, a workflow automation platform, allows any logged-in user to replay task runs and trigger batch operations belonging to other organizations without authorization checks. An attacker can exploit this to execute tasks with another organization's secrets, API keys, and environment variables, or consume their compute resources.

Technologies: trigger.dev (npm), Trigger.dev. Vendors: npm, Trigger.dev.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
High severity, with a CVSS score of 7.1, published 2 October 2026.
Which products and versions are affected?
trigger.dev (npm) <= 4.5.1; Trigger.dev unspecified.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is This vulnerability attacked?
It is attacked over the network, in a web application.
Am I affected?
Check whether you run trigger.dev (npm) or Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The POST action endpoint for run replay (`/resources/taskruns/{runId}/replay`) and batch completion (`/resources/batches/{batchId}/check-completion`) perform no authentication or authorization checks despite their respective GET loaders implementing proper user authentication. An attacker with a valid session can enumerate the predictable friendlyId values and replay any task run or trigger batch completion across organizations, gaining access to victim environment variables and secrets stored in those tasks.

Affected products

  • Trigger.dev Trigger.dev unspecified

Timeline

  • 2026-10-02: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.