CVE-2026-114091: Trigger.dev before 4.5.0 Cross-Tenant Run Payload Disclosure via API Replay Route
triggerdotdev · trigger.dev
Fixed in 4.5.0 · Affected: triggerdotdev trigger.dev before 4.5.0 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 27% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- triggerdotdev · trigger.devbefore 4.5.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Insecure Direct Object Reference
- Vendor
- triggerdotdev
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-114091 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.