Trigger.dev: Missing Authentication
Affects trigger.devSource GCVE Database
CVSS 7.1 High : upgrade to 4.5.2 soon.
Data as of 3 Oct 2026, 17:41 UTC
- Patch
- Available – fixed in 4.5.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:NWhat to do
Upgrade trigger.dev to 4.5.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtrigger.dev | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Users should update to a fixed version at or beyond 4.5.2 where authentication and authorization checks are enforced on the run replay and batch completion actions. Until patched, restrict access to the affected endpoints and monitor for unauthorized task replay or batch completion activity.
Description
Trigger.dev contains an insecure direct object reference (IDOR) vulnerability in the run replay action function where no authentication or authorization checks are performed. This allows any authenticated user to replay task runs from any organization by knowing the run's friendlyId. A similar issue exists in the batch completion action, enabling unauthorized triggering of batch completions. The vulnerability enables cross-organization task execution with victim environment secrets, resource consumption, and potential data integrity issues. Patch is available.
References
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-pp95-gc86-jq6q (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/pull/4199 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2 (opens in a new tab)