CVE-2026-114092: Trigger.dev before 4.5.0 Missing Authentication in Dashboard Run Replay Action

Published Oct 21, 2026
·
Updated

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.

Affected Software

1 affected component
Trigger.dev Trigger.dev<4.5.0

Event History

Oct 21, 2026
CVE Published
via MITRE·12:36 AM
Data Sourced
via MITRE·12:36 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What must an attacker know to exploit this issue?

The attacker needs to know a victim task run's friendlyId. No authentication or organization membership check is performed by the affected replay action handler.

2

What can an attacker do with a known run friendlyId?

They can replay the victim's run into an environment they choose. This can expose the victim's task payload or cause the task to run again using the victim's secrets.

3

Which deployments are affected?

Trigger.dev versions before 4.5.0 are affected. The vulnerable behavior is in the dashboard task-run replay route.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203