Trigger.dev authorization bypass deletes other organizations' schedules
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
Trigger.dev versions from 0 before 4.5.6 contain an authorization bypass through a user-controlled key (CWE-639) in DeleteTaskScheduleService and SetActiveOnTaskScheduleService. An authenticated user can delete or disable schedules that belong to other organizations by supplying a victim schedule's friendlyId through their own project's schedule route, which removes other organizations' IMPERATIVE cron schedules. The attacker requires low privileges and a valid account, with no user interaction. The CVSS 4.0 vector rates the impact to the availability and integrity of the affected schedules as high.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
Trigger.dev before 4.5.6 contains an authorization bypass vulnerability in DeleteTaskScheduleService and SetActiveOnTaskScheduleService that allows authenticated users to delete or disable other organizations' schedules. Attackers can send delete or disable actions through their own project's schedule route with a victim schedule friendlyId to destroy other organizations' IMPERATIVE cron schedules.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| triggerdotdev | trigger.dev | before 4.5.6 | 4.5.6 | Patch available | CNA |
- trigger.dev Vendortriggerdotdev Affected before 4.5.6 Fixed in 4.5.6 Patch available CNA
Remediation
Upgrade Trigger.dev to version 4.5.6 or later, which fixes the issue. No vendor advisory identifier is listed in the sources.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA trigger.dev (triggerdotdev) Fixed in 4.5.6
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
triggerdotdev trigger.dev 4.5.6
7 records Highest priority Priority HIGH 4 HIGH, 3 MEDIUM
Other records, highest priority first
- TI-2026-78700 Hardcoded default secrets in Trigger.dev enable authentication bypassPriority HIGH 75
- TI-2026-78697 SQL injection via tags in Trigger.dev Realtime Runs APIPriority HIGH 69
- TI-2026-78694 SQL injection in Trigger.dev TSQL compiler exposes other tenants' dataPriority HIGH 69
Timeline
- 2026-10-21 Threatist record created from CVE-2026-114078
- 2026-10-22 Priority changed: MEDIUM → LOW
- 2026-10-27 CISA SSVC decision points changed
- 2026-10-27 Priority changed: LOW → HIGH
References
More triggerdotdev vulnerabilities
- TI-2026-78700 Hardcoded default secrets in Trigger.dev enable authentication bypass CVSS 4.0CRITICAL 9.2
- TI-2026-78702 Cross-site request forgery in Trigger.dev CLI leads to token theft CVSS 4.0HIGH 8.7
- TI-2026-78696 Trigger.dev Path Traversal in Packets Presigned URL Endpoints CVSS 4.0HIGH 8.6
- TI-2026-78682 Improper authorization in Trigger.dev exposes root API key via envvars endpoint CVSS 4.0HIGH 8.6
- TI-2026-51742 Trigger.dev: Cross-tenant object store read and write via URL path traversal CVSS 3.1HIGH 8.2
- TI-2026-78699 Trigger.dev realtime streams accept unauthenticated data injection CVSS 4.0MEDIUM 6.9
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences