Is CVE-2026-114087 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114087 being exploited in the wild.

How severe is CVE-2026-114087?

High severity, with a CVSS score of 8.1, published 21 October 2026.

How is CVE-2026-114087 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-114087?

Check whether you run Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114087: Trigger.dev authentication bypass via hardcoded secrets in Docker Compose

CVE-2026-114087 · Severity: high · CVSS 8.1 · Published 2026-10-21

Trigger.dev is a workflow automation platform that can be self-hosted using Docker Compose. The default configuration file contains hardcoded cryptographic secrets that allow attackers to forge authentication tokens and log in as any user without a password. Once authenticated, attackers can access databases and internal services (PostgreSQL, Redis, ClickHouse) containing all customer data, enabling complete infrastructure compromise including data theft and manipulation.

Technologies: Trigger.dev. Vendors: Trigger.dev.

Quick answers

Is CVE-2026-114087 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114087 being exploited in the wild.
How severe is CVE-2026-114087?: High severity, with a CVSS score of 8.1, published 21 October 2026.
Which products and versions are affected?: Trigger.dev before 4.5.6.
Is there a fix for CVE-2026-114087?: Yes: fixed in 4.5.6. Until then: Do not use default secrets from hosting/docker/.env.example in production; generate strong random values for SESSION_SECRET, MAGIC_LINK_SECRET, ENCRYPTION_KEY, and MANAGED_WORKER_SECRET before deployment. Restrict network access to infrastructure services (PostgreSQL, Redis, ClickHouse) and change their default credentials. Set WHITELISTED_EMAILS to prevent auto-account creation. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114087 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-114087?: Check whether you run Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.5.6

Do not use default secrets from hosting/docker/.env.example in production; generate strong random values for SESSION_SECRET, MAGIC_LINK_SECRET, ENCRYPTION_KEY, and MANAGED_WORKER_SECRET before deployment. Restrict network access to infrastructure services (PostgreSQL, Redis, ClickHouse) and change their default credentials. Set WHITELISTED_EMAILS to prevent auto-account creation.

Technical details

The vulnerability exploits hardcoded MAGIC_LINK_SECRET in the default .env.example configuration file, which is used by remix-auth-email-link to generate AES-encrypted authentication tokens. Attackers can forge valid magic links without email delivery to authenticate as arbitrary users; session-side validation is disabled by default. Once authenticated, attackers gain network access to infrastructure services running with default credentials on shared Docker networks, leading to database and service compromise.

Affected products

Trigger.dev Trigger.dev before 4.5.6

Timeline

2026-07-21: disclosed: GitHub Security Advisory GHSA-pqxw-g93w-hj9x published
2026-10-21: advisory: NVD entry for CVE-2026-114087 published
2026-10-21: patched: Fixed in version 4.5.6

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.