Skip to main content

CVE-2026-114069: Improper Privilege Management in triggerdotdev trigger.dev

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

Description

Trigger.dev versions before 4.6.0 have an improper authorization vulnerability in the GET /api/v1/projects/:projectRef/envvars endpoint. This flaw allows users with restricted read:envvars permission to access the environment's root API key (TRIGGER_SECRET_KEY) for staging, production, and preview environments. Exploiting this, attackers can retrieve plaintext secrets, trigger tasks, and mint admin public JWTs, leading to significant privilege escalation.

CVSS v4.0

Score 8.6high

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

Affected software

triggerdotdev

trigger.dev

Affected versions
>=0 <4.6.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/21/2026, 01:33:15 UTC

Technical Analysis

CVE-2026-114069 describes an improper privilege management vulnerability in trigger.dev prior to version 4.6.0. The GET /api/v1/projects/:projectRef/envvars endpoint improperly exposes the environment's root API key (TRIGGER_SECRET_KEY) to users holding only restricted read:envvars access. This exposure enables attackers to obtain sensitive secrets in plaintext, execute tasks, and generate admin-level JWT tokens, effectively escalating their privileges within the system.

Potential Impact

Attackers with limited read:envvars permissions can escalate privileges by obtaining the root API key and plaintext secrets. This enables unauthorized triggering of tasks and minting of admin JWTs, potentially compromising the confidentiality and integrity of the environment and its data.

Mitigation Recommendations

A fix is available in trigger.dev version 4.6.0. Users should upgrade to version 4.6.0 or later to remediate this vulnerability. No additional mitigation steps are indicated beyond applying the official fix.

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:43:23.219Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad80c032cdf04f6568caa2d

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

Last enriched: 10/21/2026, 01:33:15 UTC

Last updated: 10/21/2026, 02:08:26 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