Vulnerability · Published Oct 21, 2026 · Assigned by VulnCheck
CVE-2026-114091Trigger.dev before 4.5.0 Cross-Tenant Run Payload Disclosure via API Replay Route
Medium 5.3
In plain English
A medium-severity authorization bypass via user-controlled key in trigger.dev from triggerdotdev. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 27% of all known vulnerabilities).
Severity (CVSS 3.1)5.3Medium
Exploit odds (30 days)0.3%top 72.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known
Official description
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.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| triggerdotdev | trigger.dev | 0 – before 4.5.0 |
Weakness: CWE-639 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
References
- GitHub Security Advisory (GHSA-9fq3-68cw-r7p2) vendor-advisory
- VulnCheck Advisory: Trigger.dev before 4.5.0 Cross-Tenant Run Payload Disclosure via API Replay Route third-party-advisory