Skip to main content

CVE-2026-114089: Cross-Site Request Forgery (CSRF) in triggerdotdev trigger.dev

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

Description

Trigger.dev versions before 4.5.2 have a cross-site request forgery (CSRF) vulnerability in the CLI authorization-code flow. This flaw allows an attacker to cause a logged-in user to mint a Personal Access Token (PAT) without consent by visiting a crafted URL. The attacker can then retrieve the victim's PAT from an unauthenticated API endpoint and potentially take over the user's account.

CVSS v4.0

Score 8.7high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected software

triggerdotdev

trigger.dev

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

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:27 UTC

Technical Analysis

CVE-2026-114089 describes a CSRF vulnerability in trigger.dev prior to version 4.5.2. The issue arises because accessing the /account/authorization-code/<code> endpoint mints a Personal Access Token without requiring user consent. An attacker can generate an unauthenticated authorization code, trick a logged-in user into visiting the URL, and then retrieve the victim's PAT from the unauthenticated /api/v1/token endpoint. This enables account takeover by leveraging the victim's token.

Potential Impact

Successful exploitation allows an attacker to obtain a victim's Personal Access Token without their consent, leading to potential account takeover. This compromises the victim's account security and any associated privileges or data accessible via the token.

Mitigation Recommendations

A fix is available in trigger.dev version 4.5.2. Users should upgrade to version 4.5.2 or later to remediate this 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:05.993Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad80c062cdf04f6568caa45

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

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

Last updated: 10/21/2026, 01:48:18 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