triggerdotdev trigger.dev Flaw (CVE-2026-114087) Rated CVSS 9.2
A newly published critical vulnerability in triggerdotdev trigger.dev carries a CVSS score of 9.2. Here is what is affected and how to respond.
Key points
- CVE-2026-114087 affects triggerdotdev trigger.dev.
- CVSS 9.2 (Critical).
- No exploitation confirmed yet.
triggerdotdev trigger.dev is affected by CVE-2026-114087, a security flaw that the National Vulnerability Database rates 9.2 out of 10.
At a glance
- CVE
- CVE-2026-114087
- Product
- triggerdotdev trigger.dev
- CVSS
- 9.2 Critical
- Weakness
- CWE-653
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Triggerdotdev | trigger.dev | before 4.5.6 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-114087
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-114087?
CVE-2026-114087 is a CWE-653 vulnerability in triggerdotdev trigger.dev.
How severe is CVE-2026-114087?
It has a CVSS score of 9.2 Critical.
Is CVE-2026-114087 being exploited?
There is no public confirmation of exploitation at the time of publication.
