Auth bypass in Triggerdotdev Trigger.dev
CVE-2026-114091
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.
Vulnerability class: IDOR (Insecure Direct Object Reference)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-9fq3-68cw-r7p2 (vendor-advisory)
- www.vulncheck.com/advisories/trigger-dev-before-4.5.0-cross-tenant-run-payload-… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-114091?
- CVE-2026-114091 is a medium-severity vulnerability in Triggerdotdev Trigger.dev, classified under Authorization Bypass Through User-Controlled Key. CVSS score: 5.3/10. Published 2026-10-21.
- How severe is CVE-2026-114091?
- Medium severity. CVSS v3 base score is 5.3 out of 10.