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.
References
Configurations
No configuration.
History
22 Oct 2026, 16:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-9fq3-68cw-r7p2 - | |
| References | () https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-pp95-gc86-jq6q - |
21 Oct 2026, 01:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-21 01:17
Updated : 2026-10-22 16:17
NVD link : CVE-2026-114092
Mitre link : CVE-2026-114092
CVE.ORG link : CVE-2026-114092
JSON object : View
Products Affected
No product.
CWE
CWE-306
Missing Authentication for Critical Function
