Trigger.dev before 4.5.0 looks up runs by friendlyId alone in the api.v1.runs.$runParam.replay route without scoping the lookup to the caller's runtime environment. An attacker holding any tenant's API key who knows a victim's run friendlyId can replay that run into their own environment and read the victim's task payload.
References
Configurations
No configuration.
History
28 Oct 2026, 15:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-9fq3-68cw-r7p2 - |
21 Oct 2026, 01:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-21 01:17
Updated : 2026-10-28 15:17
NVD link : CVE-2026-114091
Mitre link : CVE-2026-114091
CVE.ORG link : CVE-2026-114091
JSON object : View
Products Affected
No product.
CWE
CWE-639
Authorization Bypass Through User-Controlled Key
