Cross-site request forgery in Trigger.dev CLI leads to token theft
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Tampering
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-352.
Summary
Trigger.dev before 4.5.2 has a cross-site request forgery flaw (CWE-352) in its CLI authorization-code flow. Loading the authorization-code page mints a Personal Access Token without any consent step, so a logged-in user who opens an attacker-supplied link has a token issued. An unauthenticated attacker can then retrieve that token from the unauthenticated token endpoint and take over the victim's account.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
Trigger.dev before 4.5.2 contains a cross-site request forgery vulnerability in the CLI authorization-code flow because loading /account/authorization-code/<code> mints a Personal Access Token without any consent step. Attackers mint an unauthenticated code, lure a logged-in user to that URL, then retrieve the victim's PAT from the unauthenticated /api/v1/token endpoint to take over the account.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
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.2 | 4.5.2 | Patch available | CNA |
- trigger.dev Vendortriggerdotdev Affected before 4.5.2 Fixed in 4.5.2 Patch available CNA
Remediation
Upgrade trigger.dev to version 4.5.2 or later, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA trigger.dev (triggerdotdev) Fixed in 4.5.2
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.2
3 records Highest priority Priority HIGH 1 HIGH, 1 MEDIUM, 1 LOW
Other records, highest priority first
- TI-2026-78689 Blind SSRF in Trigger.dev via alert channel webhook URLPriority MEDIUM 57
- TI-2026-78693 Blind SSRF in Trigger.dev alert-channel webhook URLPriority LOW 24
Timeline
- 2026-10-21 Threatist record created from CVE-2026-114089
- 2026-10-22 Priority changed: MEDIUM → LOW
- 2026-10-28 CISA SSVC decision points changed
- 2026-10-28 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-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
- TI-2026-51743 Trigger.dev: Cross-tenant object read/write via path traversal in packet presign API CVSS 3.1HIGH 8.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences