Missing authentication in Trigger.dev dashboard run replay action
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-306.
Summary
Trigger.dev versions from 0 before 4.5.0 perform no authentication or organization check in the action handler of the dashboard run replay route. A remote attacker who knows a victim's run friendlyId can replay that run into an environment of their choosing, exposing the task payload or running the task again with the victim's secrets. The flaw is tracked as CWE-306 (missing authentication for a critical function).
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
Trigger.dev before 4.5.0 performs no authentication or organization check in the action handler of the dashboard run replay route (resources.taskruns.$runParam.replay) and looks up the run by friendlyId alone. A remote attacker who knows a victim's run friendlyId can replay it into an environment of their choosing, exposing the victim's task payload or running the task again with the victim's secrets.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| triggerdotdev | trigger.dev | before 4.5.0 | 4.5.0 | Patch available | CNA |
- trigger.dev Vendortriggerdotdev Affected before 4.5.0 Fixed in 4.5.0 Patch available CNA
Remediation
Upgrade trigger.dev to version 4.5.0 or later, where the affected versions are fixed. The sources list no advisory identifiers for this fix.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA trigger.dev (triggerdotdev) Fixed in 4.5.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Advisory ·
triggerdotdev trigger.dev — GitHub Security Advisory (GHSA-9fq3-68cw-r7p2)
2 records Highest priority Priority HIGH 1 HIGH, 1 MEDIUM
Other records, highest priority first
- TI-2026-78704 Authorization bypass in Trigger.dev replay route exposes run payloadsPriority MEDIUM 60
Timeline
- 2026-10-21 Threatist record created from CVE-2026-114092
- 2026-10-22 Priority changed: MEDIUM → LOW
- 2026-10-22 CISA SSVC decision points changed
- 2026-10-22 Priority changed: LOW → HIGH
References
More triggerdotdev vulnerabilities
- TI-2026-78700 Hardcoded default secrets in Trigger.dev enable authentication bypass CVSS 4.0CRITICAL 9.2
- TI-2026-78702 Cross-site request forgery in Trigger.dev CLI leads to token theft CVSS 4.0HIGH 8.7
- TI-2026-78696 Trigger.dev Path Traversal in Packets Presigned URL Endpoints CVSS 4.0HIGH 8.6
- TI-2026-78682 Improper authorization in Trigger.dev exposes root API key via envvars endpoint CVSS 4.0HIGH 8.6
- TI-2026-51742 Trigger.dev: Cross-tenant object store read and write via URL path traversal CVSS 3.1HIGH 8.2
- TI-2026-78699 Trigger.dev realtime streams accept unauthenticated data injection CVSS 4.0MEDIUM 6.9
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences