Skip to main content

CVE-2026-114091: Authorization Bypass Through User-Controlled Key in triggerdotdev trigger.dev

0
Medium
VulnerabilityCVE-2026-114091cvecve-2026-114091
Published: 10/21/2026 (10/21/2026, 00:36:56 UTC)
Source: CVE Database V5
Vendor/Project: triggerdotdev
Product: trigger.dev

Description

Trigger.dev versions before 4.5.0 have an authorization bypass vulnerability in the api.v1.runs.$runParam.replay route. The system looks up runs by friendlyId without restricting the lookup to the caller's runtime environment. An attacker with any tenant's API key who knows a victim's run friendlyId can replay that run in their own environment and access the victim's task payload.

CVSS v4.0

Score 6.0medium

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

triggerdotdev

trigger.dev

Affected versions
>=0 <4.5.0
GitHub Actionsmore threats →ai
triggerdotdev/trigger.dev
pkg:github/triggerdotdev/trigger.dev
Affected versions
>=0 <4.5.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/21/2026, 01:18:38 UTC

Technical Analysis

In trigger.dev versions prior to 4.5.0, the replay route (api.v1.runs.$runParam.replay) performs run lookups solely by friendlyId without scoping the query to the runtime environment of the caller. This allows an attacker possessing any tenant's API key and knowledge of a victim's run friendlyId to replay that run in their own environment. Consequently, the attacker can read the victim's task payload, resulting in an authorization bypass vulnerability.

Potential Impact

An attacker with limited privileges (holding any tenant's API key) can access and replay runs belonging to other tenants if they know the run's friendlyId. This leads to unauthorized disclosure of task payload data from the victim's environment, compromising confidentiality.

Mitigation Recommendations

A fix is available in trigger.dev version 4.5.0 and later. Users should upgrade to version 4.5.0 or newer to remediate this authorization bypass vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-10-20T21:46:55.741Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad80c062cdf04f6568caa47

Added to database: 10/21/2026, 00:49:10 UTC

Last enriched: 10/21/2026, 01:18:38 UTC

Last updated: 10/21/2026, 01:48:15 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses