CVE-2026-114091
Trigger.dev before 4.5.0 Cross-Tenant Run Payload Disclosure via API Replay Route
- Medium 6.0
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.
Key facts
- Published
- 21 Oct 2026
- Last changed
- 28 Oct 2026
- Assigned by
- VulnCheck
- EPSS
- 0.339% likely to be exploited in the next 30 days, higher than 27.756% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: poc; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 6.0CVSS 4.0, Mediumfrom the CNA (VulnCheck)
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N - 5.3CVSS 3.1, Mediumfrom the CNA (VulnCheck)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| triggerdotdev | trigger.dev |
|
Timeline
- 21 Oct 2026 Published