trigger.dev: Improper Isolation or Compartmentalization
CVE-2026-114087 is a high-severity improper isolation or compartmentalization vulnerability in trigger.dev from Triggerdotdev, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 4.5.6 as the first without the flaw, so updating trigger.dev to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.51% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update trigger.dev to 4.5.6 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Triggerdotdev | trigger.dev | before 4.5.6 | 4.5.6 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.2 | Critical | CNA (vulncheck.com) |
| CVSS 3.1 | 8.1 | High | CNA (vulncheck.com) |
Official description
Trigger.dev before 4.5.6 self-hosted Docker Compose deployments using the default secrets from hosting/docker/.env.example allow authentication bypass because the hardcoded MAGIC_LINK_SECRET lets anyone forge valid magic link tokens. Unauthenticated attackers can log in as any email address, then reach Postgres, Redis, and ClickHouse with default credentials from runner containers on infrastructure networks, compromising all tenant data.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Isolation or Compartmentalization
The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.
How developers prevent this class of flaw
- Break up privileges between different modules, objects, or entities. Minimize the interfaces between modules and require strong access control between them.
More Improper Isolation or Compartmentalization vulnerabilities (CWE-653)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in trigger.dev
- 8.8 High severity
- 7.9 High severity
- 7.7 High severity
- 8.1 High severity
- 8.1 High severity
- 7.7 High severity
Recent Improper Isolation or Compartmentalization vulnerabilities
- 8.8 High severity
- 8.4 High severity
- 8.8 High severity
- 9.6 Critical severity
- 7.6 High severity
- 8.3 High severity
Spotted an error? Tell us.