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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 8.3NVD modified 2026-10-21 01:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-9fq3-68cw-r7p2
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-pp95-gc86-jq6q
- https://www.vulncheck.com/advisories/trigger-dev-before-4.5.0-missing-authentication-in-dashboard-run-replay-action
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-9fq3-68cw-r7p2
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-pp95-gc86-jq6q